Delete a key from the persistent info JSON file.
AI agents call delete_persistent_info_key to permanently remove resources in Simple MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes data from persistent storage without option to recover or undo the deletion. This is irreversible data destruction, placing it in the Destructive category.
From the tool's definition Tool name explicitly states 'delete' and description confirms it 'Delete[s] a key from the persistent info JSON file' — an irreversible removal of stored data.
Attacks that exploit this kind of access
Delete a key from the persistent info JSON file. It is categorised as a Destructive tool in the Simple MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Simple MCP server in PolicyLayer and add a rule for delete_persistent_info_key: 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 Simple MCP. Nothing to install.
delete_persistent_info_key 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_persistent_info_key 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_persistent_info_key. 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_persistent_info_key is provided by the Simple MCP server (karar-hayder/simple-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 →