This record as markdown: /tools/9d9dev-mcp/list-deploys.md
What list_deploys does on 9d9dev
AI agents call list_deploys to retrieve information from 9d9dev without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
org_id | string | — | Optional. Defaults to the org_id in this project's .9d9.json — only pass to override. |
Parameters from the server's own tool schema.
Why list_deploys is rated Low
Even though list_deploys only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_deploys 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 list_deploys, this is the rule to start with:
list_deploys is read-only, so it stays allowed. 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 list_deploys call is checked against it from then on.
Questions about list_deploys
List recent static-site deploys for the org. It is categorised as a Read tool in the 9d9dev MCP Server, which means it retrieves data without modifying state.
list_deploys accepts 1 parameter: org_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 list_deploys: 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.
list_deploys is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_deploys 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 list_deploys. 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.
list_deploys 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