Search activities by description or other criteria.
AI agents call search_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.
This tool retrieves activity records from the CATS system based on search parameters. It has no side effects, does not modify data, and does not execute operations. The search pattern is characteristic of Read-category tools. Severity is low because searching existing activity records has minimal blast radius even if misused.
From the tool's definition Tool name contains 'search' and description explicitly states 'Search activities by description or other criteria' — a read-only query operation with no modification, deletion, or execution of external code.
Attacks that exploit this kind of access
Search activities by description or other criteria. 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 search_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.
search_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 search_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 search_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.
search_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 →