AI agents call list-all-tasks to retrieve information from Trigger Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists task identifiers from the worker without modifying, deleting, or executing anything. It is purely informational, making it a Read category operation. The severity is low because task ID enumeration alone does not enable direct harm; however, it could support reconnaissance for subsequent attacks. Confidence is high because the description clearly indicates a retrieval-only operation.
From the tool's definition Tool name 'list-all-tasks' and description 'List all available task IDs in the worker' indicate a query/retrieval operation with no side effects.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access list-all-tasks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trigger Dev, and nothing reaches the server without passing your rules. This is the rule we recommend for list-all-tasks:
{
"version": "1",
"default": "deny",
"tools": {
"list-all-tasks": {}
}
}list-all-tasks 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 available task IDs in the worker. It is categorised as a Read tool in the Trigger Dev MCP Server, which means it retrieves data without modifying state.
Register the Trigger Dev MCP server in PolicyLayer and add a rule for list-all-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 Trigger Dev. Nothing to install.
list-all-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-all-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-all-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-all-tasks is provided by the Trigger Dev MCP server (@triggerdotdev/trigger.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Trigger Dev tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Trigger Dev tools catalogued and risk-classified — across an index of 42,500+ MCP servers.