list_tasks
AI agents call list_tasks to retrieve information from Procrastinator 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 'list_tasks' and its placement among write operations (create/update) indicates it performs a read-only retrieval of tasks. No side effects, modifications, or destructive actions are described or implied. While the description is empty, the context is sufficiently clear to classify with high confidence as a Read operation with low severity risk.
From the tool's definition Tool name 'list_tasks' combined with server context indicating it 'allows users to list, create, and update tasks' strongly suggests this retrieves task data without modification.
Attacks that exploit this kind of access
list_tasks. It is categorised as a Read tool in the Procrastinator MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Procrastinator MCP 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 Procrastinator MCP 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 Procrastinator MCP Server MCP server (mateusjunges/procrastinator-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 →