List all requests with their basic information and summary of tasks. This provides a quick overview of all requests in the system.
AI agents call list_requests to retrieve information from TaskFlow MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though list_requests only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Documented attack patterns abuse exactly the kind of access list_requests gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TaskFlow MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_requests:
{
"version": "1",
"default": "deny",
"tools": {
"list_requests": {}
}
}list_requests is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all requests with their basic information and summary of tasks. This provides a quick overview of all requests in the system. It is categorised as a Read tool in the TaskFlow MCP MCP Server, which means it retrieves data without modifying state.
Register the TaskFlow MCP server in PolicyLayer and add a rule for list_requests: 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. Nothing to install.
list_requests 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_requests 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_requests. 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_requests is provided by the TaskFlow MCP server (pinkpixel-dev/taskflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 23 TaskFlow MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
23 TaskFlow MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.