Add stage or case-wide optional process and return details of the next assignment in the process. The API is invoked when a user tries to initiate an optional action listed under case actions which are configured and designed as a process under case wide actions or stage-only actions.
AI agents invoke add_optional_process 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 execution of a configured business process within Pega Platform. It initiates an optional process (workflow/action) on a case, causing state changes and creating assignments. This is an operational trigger that goes beyond a simple write — it executes a process flow with downstream effects depending on the process configuration, placing it in the Execute category.
From the tool's definition Add stage or case-wide optional process and return details of the next assignment in the process... invoked when a user tries to initiate an optional action... configured and designed as a process
Documented attack patterns abuse exactly the kind of access add_optional_process 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 add_optional_process:
{
"version": "1",
"default": "deny",
"tools": {
"add_optional_process": {
"limits": [
{
"counter": "add_optional_process_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}add_optional_process 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.
Add stage or case-wide optional process and return details of the next assignment in the process. The API is invoked when a user tries to initiate an optional action listed under case actions which are configured and designed as a process under case wide actions or stage-only actions. 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 add_optional_process: 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.
add_optional_process 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 add_optional_process 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 add_optional_process. 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.
add_optional_process 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.