pathrule_delete_memory
AI agents call pathrule_delete_memory 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 tool performs an irreversible deletion operation on stored memories within the path-scoped team context. This cannot be undone and represents a destructive action. While the empty description prevents full confirmation of exact semantics, the naming convention and server context strongly indicate data removal.
From the tool's definition Tool name is 'pathrule_delete_memory' — the verb 'delete' indicates irreversible removal of data. The description is empty, but context from sibling tools (pathrule_delete_rule, pathrule_delete_skill) confirms this server supports destructive operations.
Attacks that exploit this kind of access
pathrule_delete_memory. 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_memory: 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_memory 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_memory 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_memory. 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_memory 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 →