AI agents call gov.osha-inspections 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 retrieves and queries publicly available historical inspection data from the US Department of Labor Open Data Portal. It performs read-only operations (search and filter) without creating, modifying, deleting, or executing any side effects. The filtered output depends on query parameters but does not alter underlying data or trigger external operations beyond data retrieval.
From the tool's definition Tool description states 'Search OSHA inspection records' and supports filtering operations (state/city/zip, establishment name substring, OData filters) with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search OSHA inspection records via US Department of Labor Open Data Portal (~5M historical inspections). Filter by state/city/zip, establishment name substring, plus raw OData filter clauses. 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 gov.osha-inspections: 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.
gov.osha-inspections 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 gov.osha-inspections 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 gov.osha-inspections. 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.
gov.osha-inspections 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 →