get_cases

Get all cases created by authenticated user (V1 EXCLUSIVE - max 500 cases, oldest to newest). V2 users should use Data Views instead. Requires pxGetCases privilege.

ServerPega DX MCP Server
CategoryRead

How to control get_cases ↓

WHAT IT DOES

What get_cases does on Pega DX MCP Server

AI agents call get_cases to retrieve information from Pega DX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why get_cases needs a policy

This tool performs a simple data retrieval operation on cases filtered by the authenticated user. It returns up to 500 cases in chronological order. The only side effect is querying existing data with no mutations. The privilege requirement (pxGetCases) confirms it is a read-only operation. Severity is low because it only exposes data the user already has access to authenticate for.

From the tool's definition Tool description states 'Get all cases created by authenticated user' - retrieves/queries data without modification. No deletion, creation, modification, code execution, or financial operations are performed.

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

POLICY

How to control get_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 get_cases:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_cases": {}
  }
}

get_cases is read-only, so it stays allowed — but 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.

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

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_cases

What does the get_cases tool do? +

Get all cases created by authenticated user (V1 EXCLUSIVE - max 500 cases, oldest to newest). V2 users should use Data Views instead. Requires pxGetCases privilege. It is categorised as a Read tool in the Pega DX MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_cases? +

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

get_cases is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_cases? +

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

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

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

Free to start. No card required.

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