List variables available in a Census dataset. Use to discover variable codes before querying data.
AI agents call get_variables to retrieve information from Mcp Census 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 metadata about available variables in a Census dataset. It is a pure read operation that discovers schema information to support downstream queries. There are no side effects, no data modification, no code execution, and no financial impact. The low severity reflects that variable enumeration poses minimal risk; the worst case is discovery of harmless metadata.
From the tool's definition Tool name 'get_variables' and description 'List variables available in a Census dataset. Use to discover variable codes before querying data.' indicate a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
List variables available in a Census dataset. Use to discover variable codes before querying data. It is categorised as a Read tool in the Mcp Census MCP Server, which means it retrieves data without modifying state.
Register the Mcp Census MCP server in PolicyLayer and add a rule for get_variables: 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 Census. Nothing to install.
get_variables 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 get_variables 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 get_variables. 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.
get_variables is provided by the Mcp Census MCP server (petrefiedthunder/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 →