get_current_worker
Get current worker info
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 call get_current_worker to retrieve information from Trigger.dev without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions — but you may still want rate limits to control API costs.
WHY ENFORCE A POLICY ON GET_CURRENT_WORKER
Even though get_current_worker only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
RECOMMENDED POLICY
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_current_worker:
rules:
- action: allowSee the full Trigger.dev policy for all 14 tools.
DETAILS
MORE TRIGGER.DEV TOOLS
search_docs Read list_orgs Read list_projects Read list_runs Read get_run_details Read list_deploys Read list_preview_branches Read create_project_in_org Write SIMILAR READ TOOLS ON OTHER SERVERS
list_bases Airtable list_tables Airtable list_records Airtable get_record Airtable search_records Airtable search Amplitude RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the get_current_worker tool do?
Get current worker info. It is categorised as a Read tool in the Trigger.dev MCP Server, which means it retrieves data without modifying state.
How do I enforce a policy on get_current_worker?
Add a rule in your Intercept YAML policy under the tools section for get_current_worker. 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 get_current_worker?
get_current_worker is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Can I rate-limit get_current_worker?
Yes. Add a rate_limit block to the get_current_worker 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 get_current_worker completely?
Set action: deny in the Intercept policy for get_current_worker. 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 get_current_worker?
get_current_worker 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.