agent-zero/plugins/_tool_access
Alessandro ba64b57e3b Document Agent Editor workflows and policies
Replace the legacy guided-profile instructions with screenshot-led Easy and Advanced editor workflows, project availability, and A0 CLI creation.

Document sparse YAML, Markdown, and JSON overrides for identity, prompts, Tool and MCP policy, Skills visibility, and model presets. Refresh adjacent guides and remove obsolete screenshots.
2026-08-12 14:34:16 +02:00
..
extensions/python/tool_execute_before Enforce scoped tool access policies 2026-08-12 14:34:15 +02:00
webui Add thumbnails for core agent utilities 2026-08-12 14:34:15 +02:00
AGENTS.md Expose scoped plugin configuration indexes 2026-08-12 14:34:15 +02:00
default_config.yaml Unify Agent Editor capability and prompt controls 2026-08-12 14:34:15 +02:00
hooks.py Enforce scoped tool access policies 2026-08-12 14:34:15 +02:00
plugin.yaml Enforce scoped tool access policies 2026-08-12 14:34:15 +02:00
README.md Document Agent Editor workflows and policies 2026-08-12 14:34:16 +02:00

Tool Access

Tool Access is the always-enabled runtime owner for Agent Editor tool policy. Policies use the standard plugin precedence: active project profile, active project, user profile, bundled/plugin profile, then the default. Sparse project policy lives under .a0proj/plugins/_tool_access/config.json; Global profile policy lives under usr/agents/<profile>/plugins/_tool_access/config.json, and project-profile policy lives under usr/projects/<project>/.a0proj/agents/<profile>/plugins/_tool_access/config.json. The Plugins screen exposes these scoped files through its existing configuration list; policy choices remain owned by Agent Editor.

One resolver filters textual prompts and provider-native schemas, rejects local and MCP execution, and keeps delegated agents bound to their own effective scope. The required final-response capability is always available.