AI agents call job.federal-search 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 is a straightforward search/query tool that retrieves publicly available job posting data from USAJobs. It has no side effects, does not modify or delete data, does not execute code, and does not involve financial transactions. The filtering parameters are all safe lookup criteria.
From the tool's definition Tool description states it 'Search[es] current US federal job postings' with filters for keyword, title, location, etc. Core action is retrieval/query with no modification, deletion, or execution of external code.
Attacks that exploit this kind of access
Search current US federal job postings via USAJobs. Filter by keyword, positionTitle, locationName, remote, pay grade range, jobCategoryCode (occupational series), organization, whoMayApply. 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 job.federal-search: 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.
job.federal-search 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 job.federal-search 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 job.federal-search. 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.
job.federal-search 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 →