Reset the blocked search engines list (useful if engines recover from blocks).
AI agents use reset_search_engines to create or update resources in Web Search MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Web Search MCP environment.
This tool modifies the state of the application by clearing/resetting the blocked search engines list. It is a reversible write operation — it changes configuration state but does not delete data permanently or execute arbitrary code. Misuse could re-enable blocked engines, potentially bypassing rate limits or content restrictions.
From the tool's definition Reset the blocked search engines list
Documented attack patterns abuse exactly the kind of access reset_search_engines gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Web Search MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for reset_search_engines:
{
"version": "1",
"default": "deny",
"tools": {
"reset_search_engines": {
"limits": [
{
"counter": "reset_search_engines_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reset_search_engines stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Reset the blocked search engines list (useful if engines recover from blocks). It is categorised as a Write tool in the Web Search MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Web Search MCP server in PolicyLayer and add a rule for reset_search_engines: 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 Web Search MCP. Nothing to install.
reset_search_engines is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reset_search_engines 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.
Set action: deny in the PolicyLayer policy for reset_search_engines. 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.
reset_search_engines is provided by the Web Search MCP server (pranavms13/web-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Web Search MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Web Search MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.