list_candidate_activities
AI agents call list_candidate_activities 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.
The tool name strongly suggests it retrieves or queries candidate activity data within an ATS context. While the description is empty (reducing confidence slightly), the 'list_' verb conventionally indicates a read operation with no side effects. Even if misused by an agent, it would only expose existing data without the ability to modify, delete, or execute arbitrary operations.
From the tool's definition Tool name 'list_candidate_activities' indicates retrieval of activity records; prefix 'list_' is a standard pattern for querying/enumerating data without modification or deletion.
Attacks that exploit this kind of access
list_candidate_activities. 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 list_candidate_activities: 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.
list_candidate_activities 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 list_candidate_activities 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 list_candidate_activities. 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.
list_candidate_activities 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 →