// MCP TOOL REFERENCE

TRIGGER DEV TOOLS

14 tools from the Trigger Dev MCP Server, categorised by risk level.

READ TOOLS

get_current_worker Get current worker info 2/5 get_run_details Get details of a specific run 2/5 list_deploys List deployments 2/5 list_orgs List organisations 2/5 list_preview_branches List preview branches 2/5 list_projects List projects 2/5 list_runs List runs with filtering 2/5 search_docs Search Trigger.dev documentation 2/5 wait_for_run_to_complete Wait for a run to finish 2/5

WRITE TOOLS

create_project_in_org Create a project within an organisation 3/5

DESTRUCTIVE TOOLS

cancel_run Cancel an active task run 4/5

EXECUTE TOOLS

deploy Deploy tasks to an environment 5/5 initialize_project Initialise a Trigger.dev project 4/5 trigger_task Trigger a task run with a payload 5/5

// FAQ

How many tools does the Trigger Dev MCP server have? +

The Trigger Dev MCP server exposes 14 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Trigger Dev tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Trigger Dev server.

What risk categories do Trigger Dev tools fall into? +

Trigger Dev tools are categorised as Read (9), Write (1), Destructive (1), Execute (3). Each category has a recommended default policy.

Enforce policies on Trigger Dev

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →