Check currently configured default search engines
AI agents call get_engines to retrieve information from Mcp Open Webresearch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves current configuration settings—a purely informational read operation with no side effects. It has minimal blast radius; even if an agent misuses it, the only outcome is discovering which search engines are configured, which poses no security risk.
From the tool's definition Tool name 'get_engines' and description 'Check currently configured default search engines' indicate a read-only query operation that retrieves configuration state without modifying or executing anything.
Attacks that exploit this kind of access
Check currently configured default search engines. It is categorised as a Read tool in the Mcp Open Webresearch MCP Server, which means it retrieves data without modifying state.
Register the Mcp Open Webresearch MCP server in PolicyLayer and add a rule for get_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 Mcp Open Webresearch. Nothing to install.
get_engines 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_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 get_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.
get_engines is provided by the Mcp Open Webresearch MCP server (rinaldowouterson/mcp-open-webresearch). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →