AI agents call list_tasks to retrieve information from Proofhub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries task data from a todolist without any side effects. It falls squarely into the Read category as a simple data retrieval operation. Severity is low because listing tasks has minimal blast radius—an AI agent cannot cause damage by querying task lists, though context defaults could be a minor information leak concern if misapplied.
From the tool's definition Tool name is 'list_tasks' and description states it 'List tasks in a todolist' with retrieval of task metadata (completion flag, ticket number, title). No modification, deletion, or execution mentioned.
Attacks that exploit this kind of access
List tasks in a todolist (completion flag, ticket number, title). project and todolist default to context. It is categorised as a Read tool in the Proofhub MCP Server, which means it retrieves data without modifying state.
Register the Proofhub 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 Proofhub. 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 Proofhub MCP server (yashmody/proofhub-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 →