AI agents call geocode to retrieve information from Mcpzim without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Geocoding retrieves geographic coordinate data without modifying, deleting, or executing code. It has no side effects and is informational only. Severity is low due to limited blast radius—coordinate data is non-sensitive and non-destructive. Confidence is moderate (0.7) because the description is empty, requiring inference from context and sibling tools.
From the tool's definition Tool name 'geocode' with empty description. Based on sibling tools (search, get_article, plan_driving_route, route_from_places) on a ZIM archive server, geocoding—converting place names to coordinates—is a read-only data retrieval operation typical of offline…
Attacks that exploit this kind of access
geocode. It is categorised as a Read tool in the Mcpzim MCP Server, which means it retrieves data without modifying state.
Register the Mcpzim MCP server in PolicyLayer and add a rule for 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 Mcpzim. Nothing to install.
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 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 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.
geocode is provided by the Mcpzim MCP server (jasontitus/mcpzim). 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 →