job.federal-search

Search current US federal job postings via USAJobs. Filter by keyword, positionTitle, locationName, remote, pay grade range, jobCategoryCode (occupational series), organization, whoMayApply.

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/job.federal-search.md

WHAT IT DOES

What job.federal-search does on Mcp

AI agents call job.federal-search to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why job.federal-search is rated Low

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

RECOMMENDED RULE

The rule that runs job.federal-search safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For job.federal-search, this is the rule to start with:

job.federal-search Allowed

job.federal-search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "job.federal-search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every job.federal-search call is checked against it from then on.

FAQ

Questions about job.federal-search

What does the job.federal-search tool do? +

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.

How do I enforce a policy on job.federal-search? +

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.

What risk level is job.federal-search? +

job.federal-search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit job.federal-search? +

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.

How do I block job.federal-search completely? +

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.

What MCP server provides job.federal-search? +

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.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →