AI agents call delete_repo to permanently remove resources in MCPX MCP Gateway — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a repository is a destructive operation that permanently removes data and cannot be reversed. This represents the highest severity of misuse risk, as an agent calling this tool with incorrect arguments could irreversibly destroy significant amounts of code, history, and collaborative work.
From the tool's definition Tool name is 'delete_repo' and description states 'Delete a repository'. The use of 'Delete' indicates an irreversible action that cannot be undone.
Documented attack patterns abuse exactly the kind of access delete_repo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCPX MCP Gateway, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_repo:
{
"version": "1",
"default": "deny",
"hide": [
"delete_repo"
]
}delete_repo disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a repository. It is categorised as a Destructive tool in the MCPX MCP Gateway MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCPX MCP Gateway MCP server in PolicyLayer and add a rule for delete_repo: 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 MCPX MCP Gateway. Nothing to install.
delete_repo is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_repo 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 delete_repo. 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.
delete_repo is provided by the MCPX MCP Gateway MCP server (thelunarcompany/lunar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 MCPX MCP Gateway tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 MCPX MCP Gateway tools catalogued and risk-classified — across an index of 42,500+ MCP servers.