List all tasks with optional filtering
AI agents call list_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 retrieves and displays existing task data with optional filters. It has no side effects, does not create, modify, or delete data, and does not execute external operations or commit financial changes. It is purely a data retrieval operation, placing it firmly in the Read category with low severity since misuse would only expose information without causing irreversible harm or enabling destructive actions.
From the tool's definition Tool name 'list_tasks' and description 'List all tasks with optional filtering' indicate a query/retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
List all tasks with optional filtering. 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 list_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.
list_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 list_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 list_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.
list_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 →