Fetch extra information for locations using Brave Local Search API
AI agents call local_pois to retrieve information from Search MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves location information (POI: points of interest) from a search API. It is a query operation that returns data about locations without creating, modifying, deleting, or executing any operations. The action is read-only with no side effects, making it a Read category risk. Severity is low as misuse would only return informational data about locations without causing harm.
From the tool's definition Fetches extra information for locations using Brave Local Search API - retrieves location data without modification or side effects.
Attacks that exploit this kind of access
Fetch extra information for locations using Brave Local Search API. It is categorised as a Read tool in the Search MCP MCP Server, which means it retrieves data without modifying state.
Register the Search MCP server in PolicyLayer and add a rule for local_pois: 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 Search MCP. Nothing to install.
local_pois 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 local_pois 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 local_pois. 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.
local_pois is provided by the Search MCP server (nanameru/websearch-mcp). 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 →