List all tasks assigned to a specific user, optionally filtered by status
AI agents call list_tasks_by_user to retrieve information from TaskFlow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves task data without side effects. It does not create, modify, delete, or execute any operations. The optional status filter is a read-only parameter that constrains the returned results. This aligns with the Read category definition: 'retrieves or queries data; no side effects.'
From the tool's definition Tool lists and retrieves tasks assigned to a user with optional filtering by status. No creation, modification, deletion, or external execution is described.
Attacks that exploit this kind of access
List all tasks assigned to a specific user, optionally filtered by status. It is categorised as a Read tool in the TaskFlow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TaskFlow MCP Server MCP server in PolicyLayer and add a rule for list_tasks_by_user: 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 TaskFlow MCP Server. Nothing to install.
list_tasks_by_user 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_by_user 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_by_user. 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_by_user is provided by the TaskFlow MCP Server MCP server (muthupalaniappan925/taskflow-mcp-server-101). 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 →