New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_path

A destructive tool on the Mapi Agent Memory MCP server.

SERVERMapi Agent Memory SOURCEcabo0m/mapi-agent-memory
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mapi-agent-memory/delete-path.md

What delete_path does on Mapi Agent Memory

AI agents call delete_path to permanently remove resources in Mapi Agent Memory, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_path is rated Critical

The name 'delete_path' strongly suggests deletion of files or data paths without reversibility. In the context of an AI agent memory system, this represents a Destructive action. The lack of a descriptive explanation lowers confidence slightly, but the verb 'delete' is unambiguous enough to classify as Destructive rather than Execute.

From the tool's definition Tool name 'delete_path' with no description provided. The verb 'delete' indicates irreversible data removal. Given the server context (agent memory and governance), this likely removes memory records or file paths permanently.

Questions about delete_path

What does the delete_path tool do? +

delete_path is a destructive tool on the Mapi Agent Memory MCP server. It is categorised as a Destructive tool in the Mapi Agent Memory MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_path? +

Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for delete_path: 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 Mapi Agent Memory. Nothing to install.

What risk level is delete_path? +

delete_path is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_path? +

Yes. Add a rate_limit block to the delete_path 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.

How do I block delete_path completely? +

Set action: deny in the PolicyLayer policy for delete_path. 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.

What MCP server provides delete_path? +

delete_path is provided by the Mapi Agent Memory MCP server (cabo0m/mapi-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Mapi Agent Memory, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mapi Agent Memory's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.