automation_list_versions

Every version of a workflow (draft, active, archived), newest first. Returns {data: Version[]}.

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

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What automation_list_versions does on Max MCP Server

AI agents call automation_list_versions 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.

RISK

Why automation_list_versions is rated Low

Tool retrieves workflow version history without creating, modifying, or deleting data.

From the tool's definition list versions, returns data, no modification

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

automation_list_versions Allowed

automation_list_versions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "automation_list_versions": {}
  }
}

ALLOW ONLY 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_list_versions call is checked against it from then on.

FAQ

Questions about automation_list_versions

What does the automation_list_versions tool do? +

Every version of a workflow (draft, active, archived), newest first. Returns {data: Version[]}. It is categorised as a Read tool in the Max MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on automation_list_versions? +

Register the Max MCP Server MCP server in PolicyLayer and add a rule for automation_list_versions: 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_list_versions? +

automation_list_versions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit automation_list_versions? +

Yes. Add a rate_limit block to the automation_list_versions 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_list_versions completely? +

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

automation_list_versions 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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →