Perform multiple address geocoding operations in a single request. Returns results as a JSON list, showing only the first result for each. Using this to geocode POIs is strongly discouraged, as many places with the same name exist; only use this for addresses. ${commonGeocodingDescription}
AI agents call bulk-geocode to retrieve information from Stadia Maps Location API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Bulk-geocode retrieves geolocation data for provided addresses without creating, modifying, deleting, or executing arbitrary code. It is a read-only query operation that translates addresses into geographic coordinates. The low severity reflects that misuse would only expose or retrieve location data, not cause irreversible changes or execute unauthorized operations.
From the tool's definition Tool description states it performs 'multiple address geocoding operations' and 'returns results as a JSON list', which are query/retrieval operations with no modification of data.
Documented attack patterns abuse exactly the kind of access bulk-geocode gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Stadia Maps Location API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for bulk-geocode:
{
"version": "1",
"default": "deny",
"tools": {
"bulk-geocode": {}
}
}bulk-geocode 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.
Perform multiple address geocoding operations in a single request. Returns results as a JSON list, showing only the first result for each. Using this to geocode POIs is strongly discouraged, as many places with the same name exist; only use this for addresses. ${commonGeocodingDescription}. It is categorised as a Read tool in the Stadia Maps Location API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stadia Maps Location API MCP Server MCP server in PolicyLayer and add a rule for bulk-geocode: 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 Stadia Maps Location API MCP Server. Nothing to install.
bulk-geocode 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 bulk-geocode 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 bulk-geocode. 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.
bulk-geocode is provided by the Stadia Maps Location API MCP Server MCP server (stadiamaps/stadiamaps-mcp-server-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Stadia Maps Location API MCP Server, 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.
6 Stadia Maps Location API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.