MCP Server Policy

TRIGGER.DEV MCP POLICY

Enforce policies on every tool call to the Trigger.dev MCP Server. 14 tools listed, categorised, and ready for rules.

triggerdotdev/trigger.dev 8 read 6 write 14 tools total
background-jobs task-orchestration durable-execution deployment

GET STARTED

Download this policy scaffold and add your rules. Intercept enforces them on every tool call before it reaches Trigger.dev.

terminal

# Download policy scaffold

curl -o trigger-dev.yaml https://raw.githubusercontent.com/policylayer/intercept/main/policies/trigger-dev.yaml

# Run with Intercept

intercept --policy trigger-dev.yaml -- npx -y @triggerdotdev/trigger.dev

Server documentation: https://trigger.dev

READ TOOLS

8

WRITE TOOLS

2

EXECUTE TOOLS

4

POLICY YAML

This scaffold lists every tool with empty rules. Add conditions — rate limits, argument validation, deny rules — then deploy with Intercept.

trigger-dev.yaml 
version: "1"
description: "Policy for triggerdotdev/trigger.dev"
default: "allow"
tools:
    search_docs:
        rules: []
    list_orgs:
        rules: []
    list_projects:
        rules: []
    get_current_worker:
        rules: []
    list_runs:
        rules: []
    get_run_details:
        rules: []
    list_deploys:
        rules: []
    list_preview_branches:
        rules: []
    create_project_in_org:
        rules: []
    initialize_project:
        rules: []
    trigger_task:
        rules: []
    wait_for_run_to_complete:
        rules: []
    cancel_run:
        rules: []
    deploy:
        rules: []

RELATED POLICIES

Vercel 25 tools
deployment
Render 23 tools
deployment
Netlify 18 tools
deployment
CircleCI 15 tools
deployment

FREQUENTLY ASKED QUESTIONS

What tools does the Trigger.dev MCP server expose?

The Trigger.dev MCP Server exposes 14 tools across 3 categories: Read, Write, Execute. Each tool can be individually controlled with Intercept policies.

How do I enforce policies on Trigger.dev?

Download the policy scaffold, add rules (rate limits, argument validation, deny rules), then run Intercept as a proxy in front of the Trigger.dev MCP server. Every tool call is evaluated against your YAML policy before execution.

Is the Trigger.dev policy free to use?

Yes. All Intercept policies are open source under the Apache 2.0 licence. Download, modify, and deploy without restrictions.

ENFORCE POLICIES ON TRIGGER.DEV

Open source. One binary. Zero dependencies.

VIEW ON GITHUB Browse all policies →