list_tasks
AI agents call list_tasks to retrieve information from PsyFlow-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' operation pattern is a standard Read operation that retrieves information without modification or execution. No description is provided, reducing confidence slightly, but the naming convention strongly indicates a simple enumeration/querying function typical of resource discovery in MCP servers. Low severity because listing tasks presents minimal blast radius.
From the tool's definition Tool name 'list_tasks' with prefix 'list' indicates data retrieval operation with no side effects. Empty description limits direct confirmation, but naming convention and sibling context (build_task, download_task, localize) suggest this enumerates existing…
Attacks that exploit this kind of access
list_tasks. It is categorised as a Read tool in the PsyFlow-MCP MCP Server, which means it retrieves data without modifying state.
Register the PsyFlow- 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 PsyFlow-MCP. 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 PsyFlow- MCP server (taskbeacon/taskbeacon-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 →