delete_personal_info

THE RISK

Critical Risk

Why delete_personal_info needs a policy

This tool permanently removes personal information without stated undo capability. Destructive operations are more severe than Write operations because they cannot be reversed. While the server offers optional OTP authentication and encryption protections, the tool itself performs an irreversible deletion action.

From the tool's definition Tool name 'delete_personal_info' and description 'Delete specific personal information' directly indicate irreversible deletion of data.

Documented attack patterns abuse exactly the kind of access delete_personal_info gives an agent:

POLICY

How to control delete_personal_info

PolicyLayer is an MCP gateway — it sits between your AI agents and Personal Context MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_personal_info:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_personal_info"
  ]
}

delete_personal_info disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Personal Context MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Personal Context MCP Server tools

Execute disable_otp Disable OTP authentication and encryption for personal data. Execute lock_otp Immediately lock the current OTP session and block access to encrypted personal data. Requ Write batch_save_personal_info Save multiple pieces of personal information in a single request. More efficient than maki Write update_personal_info Update existing personal information Read batch_get_personal_info Retrieve multiple categories of personal information in a single request. Retrieve persona Read list_available_personal_info List all available personal information within current permissions Read otp_status Check the current OTP configuration status and whether OTP verification is required. Read verify_otp Verify an OTP token to access encrypted personal data. Required before reading encrypted i

All 9 Personal Context MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Personal Context MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_personal_info

What does the delete_personal_info tool do? +

Delete specific personal information. It is categorised as a Destructive tool in the Personal Context MCP Server 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_personal_info? +

Register the Personal Context MCP Server MCP server in PolicyLayer and add a rule for delete_personal_info: 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 Personal Context MCP Server. Nothing to install.

What risk level is delete_personal_info? +

delete_personal_info 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_personal_info? +

Yes. Add a rate_limit block to the delete_personal_info 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_personal_info completely? +

Set action: deny in the PolicyLayer policy for delete_personal_info. 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_personal_info? +

delete_personal_info is provided by the Personal Context MCP Server MCP server (matipojo/personal-context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Personal Context MCP Server tool call.

Start from Personal Context MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →