pipeline_reorder_stages
Set a new left-to-right column order. Returns {data: Stage[]} (every column).
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/pipeline-reorder-stages.md
What pipeline_reorder_stages does on Max MCP Server
AI agents use pipeline_reorder_stages 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.
Why pipeline_reorder_stages is rated Medium
Modifies pipeline stage configuration reversibly without permanent data deletion or financial impact.
From the tool's definition Set a new left-to-right column order for pipeline stages.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs pipeline_reorder_stages 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 pipeline_reorder_stages, this is the rule to start with:
pipeline_reorder_stages 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Max MCP Server, apply this rule, and every pipeline_reorder_stages call is checked against it from then on.
Questions about pipeline_reorder_stages
Set a new left-to-right column order. Returns {data: Stage[]} (every column). 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.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for pipeline_reorder_stages: 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.
pipeline_reorder_stages is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pipeline_reorder_stages 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 pipeline_reorder_stages. 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.
pipeline_reorder_stages 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