search
AI agents call search to retrieve information from WebControl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
With no description available, I rely on the tool name 'search', which strongly suggests a read/query operation. However, in the context of a headless browser automation server (which also has tools like execute_js, click, fill), 'search' could potentially trigger browser actions beyond simple data retrieval. Confidence is lowered due to the empty description.
From the tool's definition Tool name is 'search'; description is empty and uninformative.
Attacks that exploit this kind of access
search. It is categorised as a Read tool in the WebControl MCP Server, which means it retrieves data without modifying state.
Register the WebControl MCP server in PolicyLayer and add a rule for 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 WebControl. Nothing to install.
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 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 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.
search is provided by the WebControl MCP server (matansht/webcontrol). 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 →