Real-time web search. Returns ranked organic results (title, url, snippet) as JSON
AI agents call web_search to retrieve information from Superhighway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although the server implements a 'pay-per-search USDC microtransaction system', the web_search tool itself only retrieves and returns search results. The financial charge is a separate billing mechanism outside the tool's direct action. The tool's core function—querying a search engine and returning results—is a read-only operation with no destructive, modifying, or execution capabilities.
From the tool's definition Tool description states it 'Returns ranked organic results (title, url, snippet) as JSON' — purely a retrieval operation with no side effects. No data modification, deletion, code execution, or financial transaction occurs as part of the search itself.
Attacks that exploit this kind of access
Real-time web search. Returns ranked organic results (title, url, snippet) as JSON. It is categorised as a Read tool in the Superhighway MCP Server, which means it retrieves data without modifying state.
Register the Superhighway 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 Superhighway. 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 Superhighway MCP server (patwalls/superhighway-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 →