Navigate a Pega case to its next stage in the primary stage sequence. Cannot be used when case is in alternate stage or already in final stage. If no eTag is provided, automatically fetches the latest eTag from the case action for seamless operation.
AI agents invoke change_to_next_stage to trigger actions in Pega DX 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.
This tool triggers a state transition in an external system (Pega Platform), moving a case to its next stage. This is an operational action that changes workflow state in the Pega system. While it modifies state, it's not a simple data write — it executes a business process transition.
From the tool's definition Navigate a Pega case to its next stage in the primary stage sequence
Documented attack patterns abuse exactly the kind of access change_to_next_stage gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pega DX MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for change_to_next_stage:
{
"version": "1",
"default": "deny",
"tools": {
"change_to_next_stage": {
"limits": [
{
"counter": "change_to_next_stage_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}change_to_next_stage 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.
Free to start. No card required.
Navigate a Pega case to its next stage in the primary stage sequence. Cannot be used when case is in alternate stage or already in final stage. If no eTag is provided, automatically fetches the latest eTag from the case action for seamless operation. It is categorised as a Execute tool in the Pega DX MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pega DX MCP Server MCP server in PolicyLayer and add a rule for change_to_next_stage: 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 Pega DX MCP Server. Nothing to install.
change_to_next_stage 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 change_to_next_stage 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 change_to_next_stage. 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.
change_to_next_stage is provided by the Pega DX MCP Server MCP server (marco-looy/pega-dx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pega DX MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
65 Pega DX MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.