Deploy an agent to start execution. Deployment environments: - local: Runs on your machine (default) - cloud: Runs on AgentOS cloud infrastructure (requires API key) Before deployment, the agent must: - Pass all policy checks - Have valid configuration - Have necessary integrations configured ...
Part of the Agentos MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke deploy_agent to trigger processes or run actions in Agentos. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
deploy_agent can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
deploy_agent:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: true See the full Agentos policy for all 10 tools.
Agents calling execute-class tools like deploy_agent have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
deploy_agent is one of the high-risk operations in Agentos. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Deploy an agent to start execution. Deployment environments: - local: Runs on your machine (default) - cloud: Runs on AgentOS cloud infrastructure (requires API key) Before deployment, the agent must: - Pass all policy checks - Have valid configuration - Have necessary integrations configured For scheduled agents, deployment starts the scheduler. For triggered agents, deployment enables the triggers.. It is categorised as a Execute tool in the Agentos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for deploy_agent. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Agentos MCP server.
deploy_agent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the deploy_agent rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the Intercept policy for deploy_agent. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
deploy_agent is provided by the Agentos MCP server (@microsoft/agentos-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.