search_tasks
AI agents call search_tasks to retrieve information from Codebuddy MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
search_tasks appears to query or filter existing task records without creating, modifying, or deleting data. Confidence is slightly reduced due to empty description, but context from sibling tools and server purpose strongly indicate a retrieval operation. Severity is low as it only accesses task metadata with no side effects or ability to alter system state.
From the tool's definition Tool name 'search_tasks' indicates a query/retrieval operation. No description provided, but the naming pattern aligns with sibling tools (list_tasks, plan_task, update_task) that form a task management system.
Attacks that exploit this kind of access
search_tasks. It is categorised as a Read tool in the Codebuddy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Codebuddy MCP Server MCP server in PolicyLayer and add a rule for search_tasks: 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 Codebuddy MCP Server. Nothing to install.
search_tasks 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_tasks 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_tasks. 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_tasks is provided by the Codebuddy MCP Server MCP server (jacklatrobe/codebuddy-mcp). 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 →