Static risk & context dossier for a US location. Pass lat+lon or a US address (geocoded for you); optional zip adds ACS demographics. Composes five keyless federal sources: Census place context (county/state/tract/congressional district), FEMA flood zone + SFHA status, USGS ASCE 7-16 seismic desi...
AI agents call geo.location-dossier to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool has no side effects beyond data retrieval. It queries multiple public federal databases and aggregates their results into a dossier for analysis. No data is written, modified, deleted, or executed. While the underlying server settles payments in USDC, the tool itself does not move money—it merely reads structural and demographic risk data.
From the tool's definition Tool retrieves and composes static risk & context data from federal sources (Census, FEMA, USGS, NOAA, GHCN) for a US location via lat+lon or address.
Attacks that exploit this kind of access
Static risk & context dossier for a US location. Pass lat+lon or a US address (geocoded for you); optional zip adds ACS demographics. Composes five keyless federal sources: Census place context (county/state/tract/congressional district), FEMA flood zone + SFHA status, USGS ASCE 7-16 seismic design parameters (Ss/S1/SDS/SD1/seismic design category/PGA), the nearest NOAA/GHCN climate station, and Census ACS 5-year demographics (zip only). Each layer is isolated. The slow-moving structural-risk picture for siting/insurance/diligence — distinct from real-time weather/earthquake conditions. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for geo.location-dossier: 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 Mcp. Nothing to install.
geo.location-dossier 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 geo.location-dossier 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 geo.location-dossier. 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.
geo.location-dossier is provided by the MCP server (@2sio/mcp). 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 →