List available geographic levels for a dataset
AI agents call list_geographies to retrieve information from Census API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about geographic levels available in a dataset. It performs no modifications, deletions, or external operations—it is purely informational retrieval. The low severity reflects minimal risk even if misused by an AI agent, as listing metadata cannot cause harm.
From the tool's definition Tool name 'list_geographies' and description 'List available geographic levels for a dataset' indicate a retrieval operation with no side effects. The verb 'list' is explicitly enumerated as a Read category operation.
Attacks that exploit this kind of access
List available geographic levels for a dataset. It is categorised as a Read tool in the Census API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Census API MCP Server MCP server in PolicyLayer and add a rule for list_geographies: 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 Census API MCP Server. Nothing to install.
list_geographies 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 list_geographies 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 list_geographies. 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.
list_geographies is provided by the Census API MCP Server MCP server (shawndrake2/mcp-census). 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 →