automation_update

Rename or redescribe a workflow (definition changes go through automation_save_draft). Returns {data: Workflow}.

SERVERMax MCP Server SOURCEdigital-crew-technologies/max-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/digital-crew-technologies-max-mcp-server/automation-update.md

WHAT IT DOES

What automation_update does on Max MCP Server

AI agents use automation_update to create or update resources in Max MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Max MCP Server environment.

RISK

Why automation_update is rated Medium

Modifies workflow metadata reversibly without executing automation or deleting data.

From the tool's definition Rename or redescribe a workflow; definition changes

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs automation_update 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_update, this is the rule to start with:

automation_update Rate-limited

automation_update stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "automation_update": {
      "limits": [
        {
          "counter": "automation_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Max MCP Server, apply this rule, and every automation_update call is checked against it from then on.

FAQ

Questions about automation_update

What does the automation_update tool do? +

Rename or redescribe a workflow (definition changes go through automation_save_draft). Returns {data: Workflow}. It is categorised as a Write tool in the Max MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on automation_update? +

Register the Max MCP Server MCP server in PolicyLayer and add a rule for automation_update: 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.

What risk level is automation_update? +

automation_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit automation_update? +

Yes. Add a rate_limit block to the automation_update 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.

How do I block automation_update completely? +

Set action: deny in the PolicyLayer policy for automation_update. 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 automation_update? +

automation_update 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.

KEEP EXPLORING

More on Max MCP Server, and thousands of servers like it.

This server

All 415 Max MCP Server tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →