AI agents call x_search to retrieve information from Grok MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search tools retrieve data without modifying, deleting, or executing arbitrary operations. The capability is information lookup with no side effects or state changes. Low severity due to read-only nature, though confidence is slightly reduced by the empty tool description.
From the tool's definition Tool name 'x_search' and server description mentioning 'live search' indicate a search/query operation. No description provided for the tool itself, but naming and context suggest information retrieval.
Documented attack patterns abuse exactly the kind of access x_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Grok MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for x_search:
{
"version": "1",
"default": "deny",
"tools": {
"x_search": {}
}
}x_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
x_search. It is categorised as a Read tool in the Grok MCP MCP Server, which means it retrieves data without modifying state.
Register the Grok MCP server in PolicyLayer and add a rule for x_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 Grok MCP. Nothing to install.
x_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 x_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 x_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.
x_search is provided by the Grok MCP server (merterbak/grok-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Grok MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 Grok MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.