This record as markdown: /tools/cloud-easybits-easybits/web-search.md
What web_search does on EasyBits
AI agents invoke web_search to trigger actions in EasyBits. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why web_search is rated High
A 'web_search' tool typically triggers an external network operation to query the web, making it Execute category. However, because the description is empty, the exact behavior is unknown — it could be a simple read-only search or could execute more complex external operations. Severity is rated high due to potential for data exfiltration, SSRF, or unintended external requests if misused by an AI agent.
From the tool's definition Tool name is 'web_search'; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs web_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For web_search, this is the rule to start with:
web_search stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every web_search call is checked against it from then on.
Questions about web_search
web_search is a execute tool on the EasyBits MCP server. It is categorised as a Execute tool in the EasyBits MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the EasyBits 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 EasyBits. Nothing to install.
web_search is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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 EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
Across the catalogue