MCP Tool Reference High Risk

wait_for_run_to_complete

Wait for a run to finish

Part of the Trigger.dev MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

triggerdotdev/trigger.dev Execute

WHEN AI AGENTS USE THIS TOOL

AI agents invoke wait_for_run_to_complete 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 WAIT_FOR_RUN_TO_COMPLETE

wait_for_run_to_complete 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.

trigger-dev.yaml 
tools:
  wait_for_run_to_complete:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Trigger.dev policy for all 14 tools.

DETAILS

Tool Name

wait_for_run_to_complete

Category

Execute

MCP Server

Trigger.dev MCP Server

Risk Level

High

MORE TRIGGER.DEV TOOLS

trigger_task Execute
Trigger a task run with a payload
cancel_run Execute
Cancel an active run
deploy Execute
Deploy to an environment
search_docs Read
Search Trigger.dev documentation
list_orgs Read
List organisations
list_projects Read
List projects
get_current_worker Read
Get current worker info
list_runs Read
List runs with filtering

View all 14 tools →

SIMILAR EXECUTE TOOLS ON OTHER SERVERS

call-actor Apify
Call an Actor and get its run results
boot_simulator Appium
Boot an iOS simulator
setup_wda Appium
Download and setup WebDriverAgent for iOS simulators
install_wda Appium
Install and launch WebDriverAgent on an iOS simulator
auth0_deploy_action Auth0
Deploy an Auth0 action
auth0_publish_form Auth0
Publish an Auth0 form

RELATED READING

FREQUENTLY ASKED QUESTIONS

What does the wait_for_run_to_complete tool do?

Wait for a run to finish. 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 wait_for_run_to_complete?

Add a rule in your Intercept YAML policy under the tools section for wait_for_run_to_complete. 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 wait_for_run_to_complete?

wait_for_run_to_complete is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wait_for_run_to_complete?

Yes. Add a rate_limit block to the wait_for_run_to_complete 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 wait_for_run_to_complete completely?

Set action: deny in the Intercept policy for wait_for_run_to_complete. 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 wait_for_run_to_complete?

wait_for_run_to_complete 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.

VIEW ON GITHUB Full Trigger.dev policy →