Retrieve the details of a task run, e.g., status, attempts, cost, etc.
AI agents call get-run to retrieve information from Trigger Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries run information and returns status/metadata. It performs no modifications, deletions, or execution of new tasks. The word 'Retrieve' and the read-only nature of the requested data (status, attempts, cost details) confirm it is a Read operation with low severity.
From the tool's definition "Retrieve the details of a task run" with metadata like "status, attempts, cost" — pure data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access get-run gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trigger Dev, and nothing reaches the server without passing your rules. This is the rule we recommend for get-run:
{
"version": "1",
"default": "deny",
"tools": {
"get-run": {}
}
}get-run is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve the details of a task run, e.g., status, attempts, cost, etc. It is categorised as a Read tool in the Trigger Dev MCP Server, which means it retrieves data without modifying state.
Register the Trigger Dev MCP server in PolicyLayer and add a rule for get-run: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Trigger Dev. Nothing to install.
get-run is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-run rule in your PolicyLayer 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.
Set action: deny in the PolicyLayer policy for get-run. 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.
get-run is provided by the Trigger Dev MCP server (@triggerdotdev/trigger.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Trigger Dev tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Trigger Dev tools catalogued and risk-classified — across an index of 42,500+ MCP servers.