filter_companies
AI agents call filter_companies 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.
Filter operations typically retrieve and narrow datasets without modification. The tool name strongly suggests querying/filtering companies in the CATS system. However, confidence is moderate (0.7) rather than high because the description is empty, leaving some ambiguity about whether this tool might have side effects (e.g., state-changing filters or analytics triggers).
From the tool's definition Tool name 'filter_companies' indicates a search/query operation; no description provided. Sibling tools include read-like operations (attach_*_tags, authorize_*, change_*_thumbnail, change_job_status), contextualizing this within a candidate tracking system…
Attacks that exploit this kind of access
filter_companies. 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_companies: 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_companies 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_companies 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_companies. 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_companies 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 →