Get the current status of all search engines (available/blocked) and the active browser backend.
AI agents call get_search_engine_status to retrieve information from Web Search MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/status check operation that returns information about the current state of search engine availability and the active browser backend. It has no side effects, does not execute code or commands, does not create or modify data, and does not delete or move resources.
From the tool's definition Tool name 'get_search_engine_status' and description indicate it retrieves status information about search engines and browser backend without modifying any data or triggering external operations.
Documented attack patterns abuse exactly the kind of access get_search_engine_status 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 get_search_engine_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_search_engine_status": {}
}
}get_search_engine_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current status of all search engines (available/blocked) and the active browser backend. It is categorised as a Read tool in the Web Search MCP MCP Server, which means it retrieves data without modifying state.
Register the Web Search MCP server in PolicyLayer and add a rule for get_search_engine_status: 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.
get_search_engine_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_search_engine_status 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 get_search_engine_status. 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.
get_search_engine_status 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.