List all auto-deployments with triggers and file info.
AI agents call list_auto_deploys to retrieve information from Overlord MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about existing auto-deployments, their triggers, and associated file metadata. It performs no side effects—it does not create, modify, execute, or delete anything. While the Overlord C2 context involves command and control operations, the specific action here is purely informational read access.
From the tool's definition Tool name 'list_auto_deploys' and description 'List all auto-deployments with triggers and file info' indicate a query/retrieval operation with no modification or execution of deployments.
Attacks that exploit this kind of access
List all auto-deployments with triggers and file info. It is categorised as a Read tool in the Overlord MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Overlord MCP Server MCP server in PolicyLayer and add a rule for list_auto_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 Overlord MCP Server. Nothing to install.
list_auto_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_auto_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_auto_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_auto_deploys is provided by the Overlord MCP Server MCP server (skeeminator/overlord-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →