// SCAN REPORT

Pega DX MCP Server

65 tools. 36 can modify or destroy data without limits.

8 destructive tools with no built-in limits. Policy required.

Last updated: 11 Jun 2026

36 can modify or destroy data

29 read-only

65 tools total

Community server · catalogue entry verified 11/06/2026

How to control Pega DX MCP Server ↓

TOOL MAP

What Pega DX MCP Server exposes to your agents

Read (29) Write / Execute (27) Destructive / Financial (8)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Pega DX MCP Server tools

Destructive · High delete_attachment This tool permanently removes attachments from cases in Pega Platform. Destructive · High delete_case Deletion of data is the canonical Destructive operation. Destructive · Medium delete_case_follower This tool irreversibly deletes data (the follower association), matching the Destructive category definition of 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While the impact is scoped (aff Destructive · Medium delete_case_tag The tool explicitly deletes a tag from a case.

36 of Pega DX MCP Server's 65 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Pega DX MCP Server

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. These are the rules we recommend:

Deny destructive operations

{
  "delete_attachment": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_case_attachments": {
    "limits": [
      {
        "counter": "add_case_attachments_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "diagnose_pega_config": {
    "limits": [
      {
        "counter": "diagnose_pega_config_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Pega DX MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON PEGA DX →

Free to start. No card required.

FULL CATALOGUE

All 65 Pega DX MCP Server tools

DESTRUCTIVE 8 tools

Destructive delete_attachment Remove the specified attachment from a case. The API validates user authentication and privileges to delete th 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. Removes the follow 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. Only supported on data Destructive delete_participant Delete a participant from a Pega case by case ID and participant ID. If no eTag is provided, automatically fet 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 removes the link between

EXECUTE 12 tools

Execute navigate_assignment_previous Navigate back to the previously visited step in a screen flow or multi-step form assignment. If no finalETag.t Execute refresh_assignment_action Refresh assignment action form data with updated values after property changes, execute Data Transforms, and h Execute refresh_case_action Refresh case action form data with updated values after property changes, execute Data Transforms, and handle Execute change_to_next_stage Navigate a Pega case to its next stage in the primary stage sequence. Cannot be used when case is in alternate Execute change_to_stage Change to a specified stage of a case based on stageID passed. Allows navigation to any valid stage (primary, Execute jump_to_step Jump to the specified step within an assignment\ Execute perform_assignment_action Perform an assignment action to submit completed work and progress workflow. This is the FINAL step after all Execute perform_case_action Perform an action on a Pega case, updating case data and progressing the workflow. Takes the case ID and actio Execute recalculate_assignment_fields Recalculate calculated fields & whens for the current assignment action form. If no eTag is provided, automati Execute recalculate_case_action_fields Recalculate calculated fields & whens for the current case action form. If no eTag is provided, automatically Execute add_optional_process Add stage or case-wide optional process and return details of the next assignment in the process. The API is i Execute perform_bulk_action Perform case action on multiple cases simultaneously (bulk operation). Executes the specified action on all ca

WRITE 15 tools

Write add_case_attachments Attach files and/or URLs to a Pega case regardless of the context or stage of the case lifecycle. Can attach t Write add_case_followers Add multiple followers to a work object. Allows users to follow a case to receive notifications and updates ab Write add_case_tags Add multiple tags to a case Write bulk_cases_patch Perform case action on multiple cases simultaneously using PATCH /api/application/v2/cases endpoint. In Infini Write create_case Create a new Pega case. This is the FIRST step in case workflows. Automatically creates the initial assignment Write create_case_participant Create a new participant in a Pega case with specified role and participant information. If no eTag is provide Write relate_cases Create relationships between cases by relating a set of case instances to a primary case Write release_case_lock Release pessimistic lock on a Pega case and clean up any cached or pending updates. Used when canceling case o Write save_assignment_action Save assignment action form data without executing the action. Implements Write update_attachment Updates the name and category of an existing attachment for a given attachmentID. The API only updates the tit Write update_case Update a Pega case by directly modifying case properties. V1 EXCLUSIVE - only available in Traditional DX API. Write update_data_record_full Fully update an existing data record based on conditional save plan configured for a savable Data Page. Overri Write update_data_record_partial Partially update an existing data record based on conditional save plan configured for a savable Data Page. On Write update_participant Update participant details in a Pega case by case ID and participant ID. If no eTag is provided, automatically Write upload_attachment Upload a file to Pega as a temporary attachment that can later be linked to cases. Creates a temporary attachm

READ 29 tools

Read diagnose_pega_config Diagnose Pega configuration and environment variables to troubleshoot connection issues. Shows what configurat Read get_assignment Get assignment details including form fields, required fields, available actions, and eTag. Used BETWEEN case Read get_assignment_action Get detailed information about a specific action that can be performed on an assignment. Retrieves assignment Read get_attachment Get the attachment content based on the attachmentID. Returns different content types: Base64 data for file ty Read get_attachment_categories Retrieve the list of attachment categories available for a specific Pega case, filtered by attachment type (Fi Read get_case Get comprehensive case information including status, stage, assignments, and available actions. Use AFTER work Read get_case_action Get detailed information about a case action, including view metadata and available actions Read get_case_ancestors Get ancestor case hierarchy for a specific case. Retrieves ancestor hierarchy case list for the case ID passed Read get_case_attachments Get a comprehensive list of all attachments associated with a specific Pega case. Retrieves attachment metadat Read get_case_descendants Get descendants of a case instance. This API loops through all the child cases recursively descending from the Read get_case_followers Get the list of all the Case Followers. Retrieves information about users who are following a case to receive Read get_case_participants Get all participants associated with a specific Pega case. Returns comprehensive list of case participants wit Read get_case_stages Retrieve the stages list for a given case ID with processes, steps, and visited status information. Read get_case_tags Get list of tags associated to a case Read get_case_type_action Get detailed information about a case action, including view metadata and available actions Read get_case_type_bulk_action Get bulk action metadata for a specific case type and action ID Read get_case_types Get list of case types that the user can create in the application. Use returned classID as caseTypeID in crea Read get_case_view Get view details based on case ID and view name. Returns view metadata with customizable logic from pyUpgradeO Read get_case_view_calculated_fields Get calculated fields for a given case view. Retrieves only the requested calculated fields from the case view Read get_cases Get all cases created by authenticated user (V1 EXCLUSIVE - max 500 cases, oldest to newest). V2 users should Read get_data_objects Retrieve list of available data objects with metadata and HATEOAS links. Can optionally filter by data object Read get_data_view_metadata Retrieve data view metadata which includes data view parameters and list of queryable fields. Supports both qu Read get_document Get contents of a document as base64 encoded string. Downloads document content based on the documentID parame Read get_next_assignment Get detailed information about the next assignment to be performed by the requestor. Uses Get Next Work functi Read get_participant Get detailed information about a specific participant in a Pega case by case ID and participant ID. Returns pa Read get_participant_role_details Get detailed information about a specific participant role in a Pega case, including role configuration, permi Read get_participant_roles Retrieve list of participant roles for a specific Pega case. Returns available roles that can be assigned to c Read get_related_cases Get list of related cases for a specific case based on case ID Read ping_pega_service Test connectivity and system availability of Pega Infinity server using existing authentication. Makes a light

OTHER 1 tools

Other authenticate_pega Authenticate with Pega Infinity server using OAuth2 client credentials or direct access token. Stores the auth

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Pega DX MCP Server

Can an AI agent delete data through the Pega DX MCP Server MCP server? +

Yes. The Pega DX MCP Server server exposes 8 destructive tools including delete_attachment, delete_case, delete_case_follower. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Pega DX MCP Server? +

The Pega DX MCP Server server has 15 write tools including add_case_attachments, add_case_followers, add_case_tags. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Pega DX MCP Server.

How many tools does the Pega DX MCP Server MCP server expose? +

65 tools across 4 categories: Destructive, Execute, Read, Write. 29 are read-only. 36 can modify, create, or delete data.

How do I enforce a policy on Pega DX MCP Server? +

Register the Pega DX MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Pega DX MCP Server tool call.

Deterministic rules across all 65 Pega DX MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON PEGA DX →

Free to start. No card required.

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