automation_run
Fire the workflow once, now, inline — runs the draft if one exists, else the active version — and REALLY executes its actions (tasks, campaign enrolls, webhooks, signature requests). Pass prospect_id for person-scoped manual triggers. Returns {data: Run}.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/automation-run.md
What automation_run does on Max MCP Server
AI agents invoke automation_run to trigger actions in Max MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why automation_run is rated High
Triggers external operations (campaign enrolls, webhooks, signature requests) with effects determined by workflow configuration, not reversible by the tool itself.
From the tool's definition Fire the workflow...REALLY executes its actions (tasks, campaign enrolls, webhooks, signature requests).
Attacks that exploit this kind of access
The rule that runs automation_run safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For automation_run, this is the rule to start with:
automation_run stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Max MCP Server, apply this rule, and every automation_run call is checked against it from then on.
Questions about automation_run
Fire the workflow once, now, inline — runs the draft if one exists, else the active version — and REALLY executes its actions (tasks, campaign enrolls, webhooks, signature requests). Pass prospect_id for person-scoped manual triggers. Returns {data: Run}. It is categorised as a Execute tool in the Max MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for automation_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 Max MCP Server. Nothing to install.
automation_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the automation_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 automation_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.
automation_run is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
Across the catalogue