delete

THE RISK

Critical Risk

Why delete needs a policy

This tool permanently removes data from Redis without possibility of recovery through the tool itself. Deletion is the archetypal destructive operation. The high severity reflects that an AI agent could wipe critical cached data, sessions, or application state.

From the tool's definition Tool name 'delete' combined with description 'Delete one or more keys from Redis' explicitly indicates irreversible removal of data from a Redis store.

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

POLICY

How to control delete

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

policy.json

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

delete 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 MCP-Brave-Search — 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 MCP-Brave-Search tools

Execute puppeteer_evaluate Execute JavaScript in the browser console Execute puppeteer_navigate Navigate to a URL Execute puppeteer_hover Hover an element on the page Execute generate_image Generate images using EverArt Models and returns a clickable link to view the generated im Execute puppeteer_click Click an element on the page Execute puppeteer_fill Fill out an input field Execute puppeteer_select Select an element on the page with Select tag Write fork_repository Fork a GitHub repository to your account or specified organization

All 59 MCP-Brave-Search 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 MCP-Brave-Search → 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

What does the delete tool do? +

Delete one or more keys from Redis. It is categorised as a Destructive tool in the MCP-Brave-Search 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? +

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

What risk level is delete? +

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

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

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

delete is provided by the MCP-Brave-Search MCP server (modelcontextprotocol/servers-archived). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP-Brave-Search tool call.

Start from MCP-Brave-Search, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →