trigger_task
Trigger a task run with a payload
Part of the Trigger.dev MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents invoke trigger_task to trigger processes or run actions in Trigger.dev. Execute operations can have side effects beyond the immediate call — triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
WHY ENFORCE A POLICY ON TRIGGER_TASK
trigger_task can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
RECOMMENDED POLICY
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
trigger_task:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Trigger.dev policy for all 14 tools.
DETAILS
MORE TRIGGER.DEV TOOLS
wait_for_run_to_complete Execute cancel_run Execute deploy Execute search_docs Read list_orgs Read list_projects Read get_current_worker Read list_runs Read SIMILAR EXECUTE TOOLS ON OTHER SERVERS
call-actor Apify boot_simulator Appium setup_wda Appium install_wda Appium auth0_deploy_action Auth0 auth0_publish_form Auth0 RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the trigger_task tool do?
Trigger a task run with a payload. It is categorised as a Execute tool in the Trigger.dev MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
How do I enforce a policy on trigger_task?
Add a rule in your Intercept YAML policy under the tools section for trigger_task. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Trigger.dev MCP server.
What risk level is trigger_task?
trigger_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Can I rate-limit trigger_task?
Yes. Add a rate_limit block to the trigger_task rule in your Intercept 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.
How do I block trigger_task completely?
Set action: deny in the Intercept policy for trigger_task. 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.
What MCP server provides trigger_task?
trigger_task is provided by the Trigger.dev MCP server (triggerdotdev/trigger.dev). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON TRIGGER.DEV
Open source. One binary. Zero dependencies.