Search tasks by name or description
AI agents call search_tasks to retrieve information from MCP Local Database Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a retrieval operation only. It searches and returns matching tasks based on name or description criteria, with no side effects, state changes, or data modification. This is a pure read operation consistent with standard search/query functionality. Even though the server supports destructive operations (delete_task), this specific tool is limited to read access, making it the lowest risk category.
From the tool's definition Tool name 'search_tasks' and description 'Search tasks by name or description' indicate a query operation that retrieves task data without modifying it.
Attacks that exploit this kind of access
Search tasks by name or description. It is categorised as a Read tool in the MCP Local Database Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Local Database 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 MCP Local Database 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 MCP Local Database Server MCP server (manojprabhuoffl-ghub/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 →