Search the web and get ranked results with titles, URLs, and snippets.
AI agents call web_search to retrieve information from ToolCenter MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries public web search results without creating, modifying, deleting, or executing anything. It is a straightforward read operation with minimal security risk - the worst case would be an agent performing excessive searches or requesting sensitive information, but the tool itself cannot be misused to cause damage or side effects.
From the tool's definition Tool description states: 'Search the web and get ranked results with titles, URLs, and snippets.' The verb 'Search' and the outputs listed (titles, URLs, snippets) indicate pure information retrieval with no modification or execution of external systems.
Attacks that exploit this kind of access
Search the web and get ranked results with titles, URLs, and snippets. It is categorised as a Read tool in the ToolCenter MCP MCP Server, which means it retrieves data without modifying state.
Register the ToolCenter MCP server in PolicyLayer and add a rule for web_search: 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 ToolCenter MCP. Nothing to install.
web_search 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 web_search 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 web_search. 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.
web_search is provided by the ToolCenter MCP server (toolcenter-dev/mcp). 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 →