Critical Risk →

forget

Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.

Part of the Wikimedia Rest server.

forget can permanently delete data in Wikimedia Rest, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE WIKIMEDIA REST →

Free to start. No card required.

AI agents may call forget to permanently remove or destroy resources in Wikimedia Rest. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call forget in a loop, permanently destroying resources in Wikimedia Rest. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "forget"
  ]
}

See the full Wikimedia Rest policy for all 31 tools.

Get this rule live on your own Wikimedia Rest server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY WIKIMEDIA REST →

View all 31 tools →

These attack patterns abuse exactly the kind of access forget gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so forget only ever does what you allow.

SECURE WIKIMEDIA REST →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the forget tool do? +

Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.. It is categorised as a Destructive tool in the Wikimedia Rest 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 forget? +

Register the Wikimedia Rest MCP server in PolicyLayer and add a rule for forget: 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 Wikimedia Rest. Nothing to install.

What risk level is forget? +

forget 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 forget? +

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

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

forget is provided by the Wikimedia Rest MCP server (https://gateway.pipeworx.io/wikimedia-rest/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Wikimedia Rest tool call.

Deterministic rules across all 31 Wikimedia Rest tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.