AI agents call brave_local_search to retrieve information from Mcp Nexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the Brave Search API for local business and place information, then returns structured results. It retrieves data without creating, modifying, deleting, or executing operations. The 'fallback to web search if local results unavailable' mechanism is still a read operation.
From the tool's definition Tool description states it 'Search[es] for local businesses and places' and 'Returns a JSON array of results.' The verb 'search' and the output-only nature (returning results) indicate data retrieval with no modification or execution of external operations.
Attacks that exploit this kind of access
Search for local businesses and places using the Brave Search API. Implementations commonly fall back to web search if local results are unavailable. Returns a JSON array of results. It is categorised as a Read tool in the Mcp Nexus MCP Server, which means it retrieves data without modifying state.
Register the Mcp Nexus MCP server in PolicyLayer and add a rule for brave_local_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 Mcp Nexus. Nothing to install.
brave_local_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 brave_local_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 brave_local_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.
brave_local_search is provided by the Mcp Nexus MCP server (xydong-web/mcp-nexus). 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 →