delete-user-fact

THE RISK

Critical Risk

This tool irreversibly removes stored facts about the user from the Bee wearable system. Once deleted, the information cannot be recovered through normal means. While not financial or as catastrophic as a mass deletion, it represents permanent data loss that cannot be undone, making it Destructive rather than Write (which would be reversible).

From the tool's definition Tool name is 'delete-user-fact' and description states 'Delete an existing fact' with explicit instruction to 'forget information about the user, their preferences, and other details.' The verb 'delete' combined with irreversible removal of user data falls…

Documented attack patterns abuse exactly the kind of access delete-user-fact gives an agent:

HOW TO CONTROL DELETE-USER-FACT

PolicyLayer is an MCP gateway — it sits between your AI agents and BeeMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-user-fact:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-user-fact"
  ]
}

delete-user-fact 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 BeeMCP — 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

More BeeMCP tools

Destructive delete-todo Delete an existing todo. Only call this if the user explicitly says to delete a todo. Write confirm-user-fact Mark a fact as confirmed. Use this to update the confirmation status of a fact based on us Write create-todo Create a new todo for the user. Set alarm_at to an ISO 8601 formatted date-time string if Write mark-todo-completed Mark a todo as completed. Call this when a user explicitly says they Write record-user-fact Create a new fact. Use this to record new information about the user, their preferences, Write update-todo Update an existing todo. You can modify the text, completion status, or alarm time. Only i Write update-user-fact Update an existing fact. Use this to update information about the user, their preferences Read get-conversation Get the full details of a conversation by its ID. Use this to retrieve specific conversati

All 19 BeeMCP tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in BeeMCP → 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.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the delete-user-fact tool do? +

Delete an existing fact. Use this to forget information about the user, their preferences, and other details. Only call this if the user explicitly says to. It is categorised as a Destructive tool in the BeeMCP 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-user-fact? +

Register the Bee MCP server in PolicyLayer and add a rule for delete-user-fact: 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 BeeMCP. Nothing to install.

What risk level is delete-user-fact? +

delete-user-fact 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-user-fact? +

Yes. Add a rate_limit block to the delete-user-fact 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-user-fact completely? +

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

delete-user-fact is provided by the Bee MCP server (okgodoit/beemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BeeMCP tool call.

Deterministic rules across all 19 BeeMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN BEEMCP →

Free to start. No card required.

19 BeeMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT DELETE-USER-FACT ON BEEMCP DOES

// THE RISK

// HOW TO CONTROL DELETE-USER-FACT

// EXPLORE