16 tools. 10 can modify or destroy data without limits.
4 destructive tools with no built-in limits. Policy required.
Last updated:
Destructive tools (cancel_enrichment, cancel_search, delete_enrichment) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (create_enrichment, create_monitor, create_search) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Intercept sits between your agent and Exa Websets. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @exa-labs/websets-mcp-server cancel_enrichment:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
create_enrichment:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
get_enrichment:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Exa Websets server exposes 4 destructive tools including cancel_enrichment, cancel_search, delete_enrichment. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
The Exa Websets server has 6 write tools including create_enrichment, create_monitor, create_search. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
16 tools across 3 categories: Destructive, Read, Write. 6 are read-only. 10 can modify, create, or delete data.
One line change. Instead of running the Exa Websets server directly, prefix it with Intercept: intercept -c exa-labs-websets-mcp-server.yaml -- npx -y @exa-labs/websets-mcp-server. Download a pre-built policy from policylayer.com/policies/exa-labs-websets-mcp-server and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init