delete_repo_issue
AI agents call delete_repo_issue to permanently remove resources in Tangled MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of repository issues is an irreversible operation that cannot be undone. Even though the description is empty, the tool name unambiguously indicates destructive capability (delete). An AI agent misusing this could permanently remove critical project management data, issue tracking history, and associated discussions. This is more severe than Write operations and warrants the Destructive category.
From the tool's definition Tool name is 'delete_repo_issue' which explicitly performs deletion of repository issues. The sibling tools on this server include create, list, and update operations, and this is the only delete operation present, indicating irreversible data removal.
Attacks that exploit this kind of access
delete_repo_issue. It is categorised as a Destructive tool in the Tangled MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tangled MCP Server MCP server in PolicyLayer and add a rule for delete_repo_issue: 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 Tangled MCP Server. Nothing to install.
delete_repo_issue 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_issue 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_issue. 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_issue is provided by the Tangled MCP Server MCP server (zzstoatzz/tangled-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 →