relate_cases

THE RISK

Medium Risk

Why relate_cases needs a policy

This tool creates new relationship data between case entities in Pega. It modifies the state of cases by adding relational metadata, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. The 'medium' severity reflects the potential for confusion if an AI agent relates cases incorrectly, which could complicate workflow but remains fixable through reversal operations.

From the tool's definition Tool description states 'Create relationships between cases by relating a set of case instances to a primary case'. The verb 'create' and the action of establishing relationships indicates data modification.

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

POLICY

How to control relate_cases

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "relate_cases": {
      "limits": [
        {
          "counter": "relate_cases_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

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.

LIMIT 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 Destructive remove_case_document Remove a document that is linked to a specific Pega case. This operation permanently remov

All 65 Pega DX MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about relate_cases

What does the relate_cases tool do? +

Create relationships between cases by relating a set of case instances to a primary case. 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.

How do I enforce a policy on relate_cases? +

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

relate_cases is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit relate_cases? +

Yes. Add a rate_limit block to the relate_cases 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 relate_cases completely? +

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

relate_cases 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 →