Recalculate calculated fields & whens for the current case action form. If no eTag is provided, automatically fetches the latest eTag from the case action for seamless operation. Executes field calculations and when conditions based on current form state and user input. Supports recalculating spe...
AI agents invoke recalculate_case_action_fields 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.
The tool executes server-side calculations and conditional logic (field calculations and 'when' conditions) on a Pega case action form. It triggers computation and processes instructions, making it an Execute-category action. While it doesn't permanently delete data, it runs operations that can alter form state and field values.
From the tool's definition Recalculate calculated fields & whens for the current case action form... Executes field calculations and when conditions based on current form state and user input.
Documented attack patterns abuse exactly the kind of access recalculate_case_action_fields 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 recalculate_case_action_fields:
{
"version": "1",
"default": "deny",
"tools": {
"recalculate_case_action_fields": {
"limits": [
{
"counter": "recalculate_case_action_fields_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}recalculate_case_action_fields 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.
Recalculate calculated fields & whens for the current case action form. If no eTag is provided, automatically fetches the latest eTag from the case action for seamless operation. Executes field calculations and when conditions based on current form state and user input. Supports recalculating specific fields and when conditions, merging content updates, and applying page instructions during the calculation process. The API validates case and action IDs, processes calculation requests, and returns updated field values and states. 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 recalculate_case_action_fields: 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.
recalculate_case_action_fields 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 recalculate_case_action_fields 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 recalculate_case_action_fields. 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.
recalculate_case_action_fields 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.