List all current tasks with status and details
AI agents call list_tasks to retrieve information from MCP Shrimp Task Manager 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 information about tasks without creating, modifying, deleting, or executing anything. It has no destructive or irreversible effects, no code execution capability, and no financial implications. The blast radius of misuse is minimal—an AI agent could only learn about existing tasks, not alter them. This is a straightforward Read operation with low risk.
From the tool's definition Tool name 'list_tasks' and description 'List all current tasks with status and details' indicate a retrieval operation with no side effects. The verb 'list' is a classic read operation that queries existing data.
Attacks that exploit this kind of access
List all current tasks with status and details. It is categorised as a Read tool in the MCP Shrimp Task Manager MCP Server, which means it retrieves data without modifying state.
Register the MCP Shrimp Task Manager 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 Shrimp Task Manager. 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 Shrimp Task Manager MCP server (samihalawa/gist-task-manager-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 →