This record as markdown: /tools/9d9dev-mcp/activate-deploy.md
What activate_deploy does on 9d9dev
AI agents use activate_deploy to create or update resources in 9d9dev, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 9d9dev environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
org_id | string | — | Optional. Defaults to the org_id in this project's .9d9.json — only pass to override. |
deploy_id | string | Yes |
Parameters from the server's own tool schema.
Why activate_deploy is rated Medium
An AI agent can call activate_deploy faster than any human can review: one bad instruction and it creates or modifies resources in 9d9dev by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs activate_deploy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 9d9dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For activate_deploy, this is the rule to start with:
activate_deploy stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 9d9dev, apply this rule, and every activate_deploy call is checked against it from then on.
Questions about activate_deploy
Rollback / re-activate a previous deploy by id. It is categorised as a Write tool in the 9d9dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
activate_deploy accepts 2 parameters: org_id, deploy_id. Required: deploy_id. The full parameter table on this page comes from the server's own tool schema.
Register the 9d9dev MCP server in PolicyLayer and add a rule for activate_deploy: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches 9d9dev. Nothing to install.
activate_deploy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the activate_deploy rule in your PolicyLayer 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 PolicyLayer policy for activate_deploy. 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.
activate_deploy is provided by the 9d9dev MCP server (@9d9dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 9d9dev, and thousands of servers like it.
This server
Across the catalogue