Look up a US city/town/CDP via the Census geocoder, then fetch its total population from the ACS 5-year estimate. Returns: total population, area tier (major_metro / mid_metro / small_or_rural matching the adv_estimate multiplier table), row-scaling tier and target (matching the Restaurant Resear...
AI agents call census_area_profile to retrieve information from DOL WHD MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves publicly available Census Bureau demographic data through standard lookup and fetch operations. It has no side effects—it only queries and returns static information. Classification as Read is appropriate; severity is low because the data returned is non-sensitive public demographic information with no blast radius if misused by an AI agent.
From the tool's definition Tool 'look up' and 'fetch' Census data (population from ACS 5-year estimate); returns read-only demographic statistics: total population, area tier, row-scaling tier. No modifications, deletions, or external state changes.
Attacks that exploit this kind of access
Look up a US city/town/CDP via the Census geocoder, then fetch its total population from the ACS 5-year estimate. Returns: total population, area tier (major_metro / mid_metro / small_or_rural matching the adv_estimate multiplier table), row-scaling tier and target (matching the Restaurant Research Agent. It is categorised as a Read tool in the DOL WHD MCP MCP Server, which means it retrieves data without modifying state.
Register the DOL WHD MCP server in PolicyLayer and add a rule for census_area_profile: 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 DOL WHD MCP. Nothing to install.
census_area_profile 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 census_area_profile 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 census_area_profile. 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.
census_area_profile is provided by the DOL WHD MCP server (uhq-actual/dol_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 →