geocode_us_address
Geocode one U.S., Puerto Rico, or U.S. Island Areas address through the public Census Geocoder. Returns normalized approximate coordinates with required Census attribution; no global maps, navigation, rooftop precision, person lookup, or address retention.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/geocode-us-address.md
What geocode_us_address does on Delx MCP Server
AI agents call geocode_us_address to retrieve information from Delx MCP Server 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 |
|---|---|---|---|
address | string | Yes | One U.S., Puerto Rico, or U.S. Island Areas address. |
timeout | integer | — | |
benchmark | string | — |
Parameters from the server's own tool schema.
Why geocode_us_address is rated Low
This tool queries a public geocoding service and returns location data without creating, modifying, deleting, or executing operations. It is purely a data retrieval function. The emphasis on 'no address retention' and 'approximate coordinates' (not precision) further reduces risk.
From the tool's definition The tool 'geocode_us_address' retrieves coordinates from a public Census Geocoder service. The description explicitly states it 'Returns normalized approximate coordinates' and 'no address retention', indicating read-only data retrieval with no side effects,…
Attacks that exploit this kind of access
The rule that runs geocode_us_address safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For geocode_us_address, this is the rule to start with:
geocode_us_address 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 Delx MCP Server, apply this rule, and every geocode_us_address call is checked against it from then on.
Questions about geocode_us_address
Geocode one U.S., Puerto Rico, or U.S. Island Areas address through the public Census Geocoder. Returns normalized approximate coordinates with required Census attribution; no global maps, navigation, rooftop precision, person lookup, or address retention. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
geocode_us_address accepts 3 parameters: address, timeout, benchmark. Required: address. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for geocode_us_address: 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 Delx MCP Server. Nothing to install.
geocode_us_address 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_us_address 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_us_address. 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_us_address is provided by the Delx MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue