pathrule_delete_rule
AI agents call pathrule_delete_rule to permanently remove resources in Pathrule — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete' prefix is strong evidence of a destructive action that cannot be undone. In the context of 'path-scoped team memories, rules and skills for AI coding agents,' deleting a rule would permanently remove configuration or governance data that agents depend on. This could cause cascading failures in agent behavior or coding workflows.
From the tool's definition Tool name 'pathrule_delete_rule' contains 'delete', which indicates irreversible removal of data. The description is empty, but sister tools include 'pathrule_delete_memory' and 'pathrule_delete_skill', establishing a pattern of destructive operations on this…
Attacks that exploit this kind of access
pathrule_delete_rule. It is categorised as a Destructive tool in the Pathrule MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pathrule MCP server in PolicyLayer and add a rule for pathrule_delete_rule: 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 Pathrule. Nothing to install.
pathrule_delete_rule 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 pathrule_delete_rule 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 pathrule_delete_rule. 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.
pathrule_delete_rule is provided by the Pathrule MCP server (pathrule/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 →