Home / Features / Agents / Tool scope per agent

Tool-scope-per-agent permissions on osFoundry

osFoundry restricts which tools each agent can call. The research agent gets web search and the browser; the code agent gets shell and file ops; the customer-success agent gets only email and the KB reader. Tool scope is part of the agent profile, versioned in osStudio, and enforced at the orchestrator level — agents can’t silently widen their own permissions.

Quick answer

Per-profile allowlist of tools an agent can call.
Enforced at orchestrator level — not just system-prompt advice.
Workspace policies override per-profile (workspace-wide bans).

Frequently asked questions

What happens if an agent tries to call a tool it doesn’t have?

The call is rejected with an audit-logged error before reaching the tool.

Can I add custom tools to a profile?

Yes — any plugin or MCP-served tool can be scoped to a profile.

Related features