Find one specific place or brand location by its proper name or unique brand. Use only when the user's query includes a distinct title (e.g., "The Met", "Starbucks Reserve Roastery") or a brand they want all nearby branches of (e.g., "Macy's stores near me"). Do not use for generic place types su...
Risk signalsHigh parameter count (19 properties)
Part of the Mapbox server.
Free to start. No card required.
AI agents call poi_search_tool to retrieve information from Mapbox without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though poi_search_tool only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"poi_search_tool": {}
}
}See the full Mapbox policy for all 9 tools.
These attack patterns abuse exactly the kind of access poi_search_tool gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Find one specific place or brand location by its proper name or unique brand. Use only when the user's query includes a distinct title (e.g., "The Met", "Starbucks Reserve Roastery") or a brand they want all nearby branches of (e.g., "Macy's stores near me"). Do not use for generic place types such as 'museums', 'coffee shops', 'tacos', etc. Setting a proximity point is strongly encouraged for more relevant results. Always try to use a limit of at least 3 in case the user's intended result is not the first result. Supports both JSON and text output formats.. It is categorised as a Read tool in the Mapbox MCP Server, which means it retrieves data without modifying state.
Register the Mapbox MCP server in PolicyLayer and add a rule for poi_search_tool: 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 Mapbox. Nothing to install.
poi_search_tool 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 poi_search_tool 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 poi_search_tool. 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.
poi_search_tool is provided by the Mapbox MCP server (Waldzell-Agentics/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Mapbox tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.