Find all ZIP codes within a given radius of a center ZIP code. Returns each nearby ZIP with its distance from the center.
AI agents call find_zip_codes_in_radius to retrieve information from loc8n Geographic Data without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sort | string | — | Sort order for results |
unit | string | — | Distance unit |
limit | integer | — | Maximum number of results (1 to 500, default 100) |
radius | number | Yes | Search radius (0.1 to 500) |
zipCode | string | Yes | Center ZIP code (5 digits) |
Parameters from the server's own tool schema.
This tool queries geographic/demographic data and returns results without creating, modifying, deleting, or executing any operations. It is a straightforward read-only lookup that retrieves pre-existing ZIP code information based on spatial proximity calculations. No side effects or irreversible actions are possible.
From the tool's definition Tool name 'find_zip_codes_in_radius' and description 'Find all ZIP codes within a given radius of a center ZIP code.
Attacks that exploit this kind of access
Find all ZIP codes within a given radius of a center ZIP code. Returns each nearby ZIP with its distance from the center. It is categorised as a Read tool in the loc8n Geographic Data MCP Server, which means it retrieves data without modifying state.
find_zip_codes_in_radius accepts 5 parameters: sort, unit, limit, radius, zipCode. Required: radius, zipCode. The full parameter table on this page comes from the server's own tool schema.
Register the loc8n Geographic Data MCP server in PolicyLayer and add a rule for find_zip_codes_in_radius: 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 loc8n Geographic Data. Nothing to install.
find_zip_codes_in_radius 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 find_zip_codes_in_radius 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 find_zip_codes_in_radius. 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.
find_zip_codes_in_radius is provided by the loc8n Geographic Data MCP server (gener8v/gener8v.mcp.geographic-data). 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 →