Create a new Pega case. This is the FIRST step in case workflows. Automatically creates the initial assignment (returned in nextAssignmentInfo). Many case types accept empty content {}. If fields required, automatic field discovery provides guidance. Returns: caseID, assignmentID (in nextAssignme...
AI agents use create_case to create or update resources in Pega DX MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pega DX MCP Server environment.
This tool creates new data structures (cases and assignments) in a business process management system. While case creation is typically reversible (cases can be closed, archived, or deleted), it initiates workflows that may trigger downstream business logic, notifications, or state transitions in the Pega system.
From the tool's definition 'Create a new Pega case' — the tool creates new data (a case) in the Pega Platform, which is a reversible operation.
Documented attack patterns abuse exactly the kind of access create_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 create_case:
{
"version": "1",
"default": "deny",
"tools": {
"create_case": {
"limits": [
{
"counter": "create_case_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_case 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.
Free to start. No card required.
Create a new Pega case. This is the FIRST step in case workflows. Automatically creates the initial assignment (returned in nextAssignmentInfo). Many case types accept empty content {}. If fields required, automatic field discovery provides guidance. Returns: caseID, assignmentID (in nextAssignmentInfo.ID), eTag. Next steps: use get_assignment with assignmentID to view form fields. 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.
Register the Pega DX MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_case is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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.