filter_jobs
AI agents call filter_jobs to retrieve information from CATS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on naming convention and the broader CATS ATS context (candidate management, job tracking), 'filter_jobs' most likely retrieves or queries job records without side effects. The 'filter_' prefix is typically associated with Read operations (search, list, filter). The empty description prevents confirmation of side effects, but no evidence suggests mutation, deletion, or execution.
From the tool's definition Tool name 'filter_jobs' indicates querying/filtering operations with no explicit data modification or deletion capability. The '_jobs' suffix and context within a recruiting system suggests retrieval of job records based on criteria.
Attacks that exploit this kind of access
filter_jobs. It is categorised as a Read tool in the CATS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CATS MCP Server MCP server in PolicyLayer and add a rule for filter_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 CATS MCP Server. Nothing to install.
filter_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 filter_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 filter_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.
filter_jobs is provided by the CATS MCP Server MCP server (vanman2024/cats-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 →