Remove related work association between two cases by deleting a specific relationship
AI agents call delete_related_case to permanently remove resources in Pega DX MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a relationship between cases, which cannot be undone. While it does not delete the cases themselves, it irreversibly removes an association. In Pega workflow systems, case relationships often represent critical business process dependencies and audit trails. Unauthorized deletion could break process logic, hide audit history, or corrupt case hierarchies.
From the tool's definition Tool name 'delete_related_case' and description 'Remove related work association between two cases by deleting a specific relationship' indicate irreversible deletion of data (the relationship/association between cases).
Documented attack patterns abuse exactly the kind of access delete_related_case 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 delete_related_case:
{
"version": "1",
"default": "deny",
"hide": [
"delete_related_case"
]
} delete_related_case disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove related work association between two cases by deleting a specific relationship. It is categorised as a Destructive tool in the Pega DX MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pega DX MCP Server MCP server in PolicyLayer and add a rule for delete_related_case: 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.
delete_related_case is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_related_case 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 delete_related_case. 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.
delete_related_case 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.