automation_get_run
One run with per-step states, outputs and errors (403 for document-triggered runs without a member session). Returns {data: Run}.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/automation-get-run.md
What automation_get_run does on Max MCP Server
AI agents call automation_get_run to retrieve information from Max MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why automation_get_run is rated Low
Tool retrieves automation run state and outputs without modifying data or triggering actions.
From the tool's definition One run with per-step states, outputs and errors. Returns data.
Attacks that exploit this kind of access
The rule that runs automation_get_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_get_run, this is the rule to start with:
automation_get_run is read-only, so it stays allowed. 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_get_run call is checked against it from then on.
Questions about automation_get_run
One run with per-step states, outputs and errors (403 for document-triggered runs without a member session). Returns {data: Run}. It is categorised as a Read tool in the Max MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for automation_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 Max MCP Server. Nothing to install.
automation_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 automation_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 automation_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.
automation_get_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.
This server
Across the catalogue