Delete a specific cloned repo from the temp folder to free up disk space.
AI agents call delete_cloned_repo to permanently remove resources in Spring Api Intel — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes cloned repositories from the temp folder. While the blast radius is somewhat limited (temporary folder contents, not production data), the destructive nature of permanent deletion and inability to recover the data justifies the Destructive category and high severity. Confidence is high due to explicit 'Delete' language in the description.
From the tool's definition Tool performs 'Delete a specific cloned repo' which irreversibly removes data from disk. The action cannot be undone and permanently frees disk space by deleting repository files.
Attacks that exploit this kind of access
Delete a specific cloned repo from the temp folder to free up disk space. It is categorised as a Destructive tool in the Spring Api Intel MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Spring Api Intel MCP server in PolicyLayer and add a rule for delete_cloned_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 Spring Api Intel. Nothing to install.
delete_cloned_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_cloned_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_cloned_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_cloned_repo is provided by the Spring Api Intel MCP server (mparth14/spring-api-intel-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 →