AI agents call list_requests to retrieve information from MCP TaskManager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation to enumerate requests. It has no side effects, does not execute code, does not modify data, and does not delete or move resources. The blast radius of misuse is minimal—an agent querying request metadata presents negligible risk.
From the tool's definition Tool name 'list_requests' and description 'List all requests in the system' indicate a query operation that retrieves data without modifying or deleting it.
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 MCP TaskManager, 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 in the system. It is categorised as a Read tool in the MCP TaskManager MCP Server, which means it retrieves data without modifying state.
Register the MCP TaskManager 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 MCP TaskManager. 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 MCP TaskManager MCP server (rudra-ravi/mcp-taskmanager). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP TaskManager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 MCP TaskManager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.