AI agents call fetch_jobs to retrieve information from Crosswalk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries job data across multiple ATS systems. Fetching and filtering job listings produces no side effects, does not modify or delete data, and does not execute arbitrary code or trigger external operations. This is a classic Read operation with minimal blast radius if misused (worst case: retrieving unintended job listings).
From the tool's definition Tool description states 'Fetch live jobs' with filters—a retrieval operation with no modification, deletion, or execution of external code. The verb 'fetch' and the context of querying job listings indicate a read-only operation.
Attacks that exploit this kind of access
Fetch live jobs across configured ATSs with filters (title, location, H-1B, etc). It is categorised as a Read tool in the Crosswalk MCP Server, which means it retrieves data without modifying state.
Register the Crosswalk MCP server in PolicyLayer and add a rule for fetch_jobs: 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 Crosswalk. Nothing to install.
fetch_jobs 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 fetch_jobs 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 fetch_jobs. 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.
fetch_jobs is provided by the Crosswalk MCP server (mohakgarg5/crosswalk-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 →