List all tasks with a specific status
AI agents call list_tasks_by_status to retrieve information from Valkey MCP Task Management Server 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 query to list/filter tasks by their status. It retrieves existing data with no side effects, no code execution, and no modifications. This is a straightforward Read operation with minimal blast radius even if misused—at worst an AI agent could enumerate all tasks, which poses low security risk.
From the tool's definition Tool name 'list_tasks_by_status' and description 'List all tasks with a specific status' indicate a query operation that retrieves and filters task data without modifying state.
Documented attack patterns abuse exactly the kind of access list_tasks_by_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Valkey MCP Task Management Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_tasks_by_status:
{
"version": "1",
"default": "deny",
"tools": {
"list_tasks_by_status": {}
}
}list_tasks_by_status 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 tasks with a specific status. It is categorised as a Read tool in the Valkey MCP Task Management Server MCP Server, which means it retrieves data without modifying state.
Register the Valkey MCP Task Management Server MCP server in PolicyLayer and add a rule for list_tasks_by_status: 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 Valkey MCP Task Management Server. Nothing to install.
list_tasks_by_status 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_status 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_status. 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_status is provided by the Valkey MCP Task Management Server MCP server (jbrinkman/valkey-ai-tasks). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Valkey MCP Task Management Server, 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.
17 Valkey MCP Task Management Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.