// MCP TOOL REFERENCE

remove_case_document

ServerPega DX MCP Server
CategoryDestructive

WHAT IT DOES

What remove_case_document does on Pega DX MCP Server

AI agents call remove_case_document 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.

THE RISK

Critical Risk

Why remove_case_document needs a policy

This tool performs an irreversible operation that cannot be undone. While it removes a link rather than deleting the document itself, the permanent removal of the association between document and case constitutes destructive action.

From the tool's definition The tool description explicitly states 'permanently removes the link between the document and the case' and 'Remove a document that is linked to a specific Pega case'. The use of 'permanently' and 'remove' indicates irreversible deletion or unlinking of data.

Documented attack patterns abuse exactly the kind of access remove_case_document gives an agent:

POLICY

How to control remove_case_document

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 remove_case_document:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_case_document"
  ]
}

remove_case_document disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Pega DX MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Pega DX MCP Server tools

Destructive delete_attachment Remove the specified attachment from a case. The API validates user authentication and pri Destructive delete_case Delete a case that is currently in the create stage Destructive delete_case_follower Remove a follower from a case, ending their subscription to case notifications and updates Destructive delete_case_tag Delete a specific tag from a case by case ID and tag ID Destructive delete_data_record Delete a data record based on conditional save plan configured for a savable Data Page. On Destructive delete_participant Delete a participant from a Pega case by case ID and participant ID. If no eTag is provide Destructive delete_related_case Remove related work association between two cases by deleting a specific relationship Execute navigate_assignment_previous Navigate back to the previously visited step in a screen flow or multi-step form assignmen

All 65 Pega DX MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Pega DX MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about remove_case_document

What does the remove_case_document tool do? +

Remove a document that is linked to a specific Pega case. This operation permanently removes the link between the document and the case. The document ID and case ID must both be valid and the user must have appropriate permissions to remove documents from the case. 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.

How do I enforce a policy on remove_case_document? +

Register the Pega DX MCP Server MCP server in PolicyLayer and add a rule for remove_case_document: 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.

What risk level is remove_case_document? +

remove_case_document is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_case_document? +

Yes. Add a rate_limit block to the remove_case_document 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.

How do I block remove_case_document completely? +

Set action: deny in the PolicyLayer policy for remove_case_document. 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.

What MCP server provides remove_case_document? +

remove_case_document 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.

Enforce policy on every Pega DX MCP Server tool call.

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.

CHECK YOUR STACK →

Free to start. No card required.

65 Pega DX MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.