Release pessimistic lock on a Pega case and clean up any cached or pending updates. Used when canceling case operations that require locking.
AI agents use release_case_lock to create or update resources in Pega DX MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pega DX MCP Server environment.
This tool modifies case state by releasing locks and cleaning up pending updates—operations that are reversible and don't permanently delete data or execute arbitrary code. It falls under Write rather than Destructive because the changes can be undone (re-locking, re-submitting updates).
From the tool's definition Tool description states it 'Release[s] pessimistic lock on a Pega case and clean up any cached or pending updates.' The action modifies the lock state and clears cached updates, which are reversible state changes.
Documented attack patterns abuse exactly the kind of access release_case_lock 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 release_case_lock:
{
"version": "1",
"default": "deny",
"tools": {
"release_case_lock": {
"limits": [
{
"counter": "release_case_lock_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}release_case_lock 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.
Free to start. No card required.
Release pessimistic lock on a Pega case and clean up any cached or pending updates. Used when canceling case operations that require locking. It is categorised as a Write tool in the Pega DX MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pega DX MCP Server MCP server in PolicyLayer and add a rule for release_case_lock: 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.
release_case_lock 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 release_case_lock 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 release_case_lock. 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.
release_case_lock 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.