geocode
Forward geocode an address or place name to coordinates. Uses Nominatim (free, no key). Returns lat, lon, display_name, type, and importance for up to 5 results. Parameters: query — Address or place name to geocode (required), e.g. "London" or "10 Downing Street".
This record as markdown: /tools/com-gadgethumans-swarm-x402-middleware/geocode.md
What geocode does on X402 Middleware
AI agents call geocode to retrieve information from X402 Middleware without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes |
Parameters from the server's own tool schema.
Why geocode is rated Low
The geocode tool performs a lookup operation against Nominatim to convert human-readable addresses into coordinates and metadata. This is purely informational retrieval with no ability to modify, delete, execute code, or affect financial systems. The tool has minimal blast radius if misused by an agent—it can only return publicly available geographic information.
From the tool's definition Tool description states it 'Forward geocode an address or place name to coordinates' and 'Returns lat, lon, display_name, type, and importance for up to 5 results.' This is a query operation that retrieves geographic data with no side effects or modifications.
Attacks that exploit this kind of access
The rule that runs geocode safely
PolicyLayer is an MCP gateway: it sits between your AI agents and X402 Middleware, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For geocode, this is the rule to start with:
geocode is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect X402 Middleware, apply this rule, and every geocode call is checked against it from then on.
Questions about geocode
Forward geocode an address or place name to coordinates. Uses Nominatim (free, no key). Returns lat, lon, display_name, type, and importance for up to 5 results. Parameters: query — Address or place name to geocode (required), e.g. "London" or "10 Downing Street". It is categorised as a Read tool in the X402 Middleware MCP Server, which means it retrieves data without modifying state.
geocode accepts 1 parameter: query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the X402 Middleware 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 X402 Middleware. 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 X402 Middleware MCP server (@gadgethumans/x402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on X402 Middleware, and thousands of servers like it.
This server
Across the catalogue