Search for jobs on Lever job boards across multiple companies
AI agents call search_lever_jobs to retrieve information from Job Search MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries job listings from Lever job boards. It is a search/query operation that returns information without creating, modifying, deleting, or executing code. No sensitive actions like payments, data destruction, or code execution are involved. The blast radius of misuse is minimal—an agent could retrieve irrelevant job results but cannot cause harm.
From the tool's definition Tool name contains 'search' and description states 'Search for jobs on Lever job boards' - a query operation with no side effects or data modifications.
Attacks that exploit this kind of access
Search for jobs on Lever job boards across multiple companies. It is categorised as a Read tool in the Job Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Job Search MCP Server MCP server in PolicyLayer and add a rule for search_lever_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 Job Search MCP Server. Nothing to install.
search_lever_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 search_lever_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 search_lever_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.
search_lever_jobs is provided by the Job Search MCP Server MCP server (prabhakar1234pr/applying-jobs-mcp-server). 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 →