Critical Risk →

search_write

Write search operations: clear, delete, move indices

Can clear or delete entire search indices

Part of the Algolia MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@algolia/mcp Destructive

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

Without a policy, an AI agent could call search_write in a loop, permanently destroying resources in Algolia. There is no undo for destructive operations. Intercept 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.

algolia.yaml
tools:
  search_write:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Algolia policy for all 10 tools.

Tool Name search_write
Category Destructive
MCP Server Algolia MCP Server
Risk Level Critical

View all 10 tools →

Agents calling destructive-class tools like search_write have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

search_write is one of the critical-risk operations in Algolia. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the search_write tool do? +

Write search operations: clear, delete, move indices. It is categorised as a Destructive tool in the Algolia 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 search_write? +

Add a rule in your Intercept YAML policy under the tools section for search_write. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Algolia MCP server.

What risk level is search_write? +

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

Yes. Add a rate_limit block to the search_write rule in your Intercept 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 search_write completely? +

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

search_write is provided by the Algolia MCP server (@algolia/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

Currently onboarding teams running MCP in production.
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.

// REQUEST EARLY ACCESS

We're letting people in as fast as we can.

You're in the queue.

We'll be in touch as soon as we can let you in.