Low Risk

brave_local_search

Searches for local businesses and places using Brave

How to control brave_local_search ↓

What brave_local_search does on MCP-Brave-Search

AI agents call brave_local_search to retrieve information from MCP-Brave-Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why brave_local_search needs a policy

This tool performs a search query to retrieve information about local businesses and places. Search operations are read-only with no side effects, destructive capability, or financial impact. The low severity reflects minimal risk even if misused by an agent, as it only retrieves publicly available information.

From the tool's definition Tool name 'brave_local_search' and description 'Searches for local businesses and places using Brave' indicate a search/query operation that retrieves information without modifying state.

Documented attack patterns abuse exactly the kind of access brave_local_search gives an agent:

How to control brave_local_search

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Brave-Search, and nothing reaches the server without passing your rules. This is the rule we recommend for brave_local_search:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "brave_local_search": {}
  }
}

brave_local_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP-Brave-Search — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about brave_local_search

What does the brave_local_search tool do? +

Searches for local businesses and places using Brave. It is categorised as a Read tool in the MCP-Brave-Search MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on brave_local_search? +

Register the MCP-Brave-Search 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-Brave-Search. Nothing to install.

What risk level is brave_local_search? +

brave_local_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit brave_local_search? +

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.

How do I block brave_local_search completely? +

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.

What MCP server provides brave_local_search? +

brave_local_search is provided by the MCP-Brave-Search MCP server (modelcontextprotocol/servers-archived). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP-Brave-Search tool call.

Start from MCP-Brave-Search, 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.

59 MCP-Brave-Search tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.