Get descendants of a case instance. This API loops through all the child cases recursively descending from the specific one, and returns the assignments and actions for each. If the current user does not have access to a given child case, they can only see limited information, and can not drill d...
AI agents call get_case_descendants 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.
This tool retrieves hierarchical case data and displays information to the user. It has no side effects—it does not create, modify, delete, or execute operations. The access restrictions confirm it is a read-only query operation with appropriate permission boundaries. Severity is low because querying case metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description states it 'Get descendants of a case instance' and 'returns the assignments and actions for each'. Uses passive retrieval language ('returns', 'see') with no modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access get_case_descendants 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 get_case_descendants:
{
"version": "1",
"default": "deny",
"tools": {
"get_case_descendants": {}
}
}get_case_descendants is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get descendants of a case instance. This API loops through all the child cases recursively descending from the specific one, and returns the assignments and actions for each. If the current user does not have access to a given child case, they can only see limited information, and can not drill down into any child cases. It is categorised as a Read tool in the Pega DX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pega DX MCP Server MCP server in PolicyLayer and add a rule for get_case_descendants: 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.
get_case_descendants is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_case_descendants 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 get_case_descendants. 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.
get_case_descendants 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.