Refresh case action form data with updated values after property changes, execute Data Transforms, and handle table row operations in modals. If no eTag is provided, automatically fetches the latest eTag from the case action for seamless operation. Supports form refresh settings configured in Flo...
AI agents invoke refresh_case_action 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.
While the tool modifies form data (which could suggest Write category), the key distinguishing factor is that it executes Data Transforms and processes Flow Actions—these are code/logic execution operations in the Pega platform whose side effects are determined by system configuration rather than data content alone. The tool triggers computational operations on the Pega backend that go beyond simple CRUD operations.
From the tool's definition Tool description states it 'execute[s] Data Transforms' and 'handle[s] table row operations in modals' with 'form refresh settings configured in Flow Action rules' and 'embedded list operations'.
Documented attack patterns abuse exactly the kind of access refresh_case_action 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 refresh_case_action:
{
"version": "1",
"default": "deny",
"tools": {
"refresh_case_action": {
"limits": [
{
"counter": "refresh_case_action_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}refresh_case_action 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.
Refresh case action form data with updated values after property changes, execute Data Transforms, and handle table row operations in modals. If no eTag is provided, automatically fetches the latest eTag from the case action for seamless operation. Supports form refresh settings configured in Flow Action rules, generative AI form filling, and embedded list operations with comprehensive validation and preprocessing execution. The API validates case and action IDs, retrieves view data, and returns information about fields affected by the refresh action. Supports Pega Infinity \. 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 refresh_case_action: 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.
refresh_case_action 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 refresh_case_action 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 refresh_case_action. 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.
refresh_case_action 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.