jump_to_step

THE RISK

High Risk

Why jump_to_step needs a policy

This tool executes a workflow action by jumping to a specific step in an assignment, which triggers external operations within the Pega Platform. It is not merely reading data, nor does it create/modify data in a straightforward reversible way — it advances or redirects workflow execution state, making it an Execute-category action. Misuse could cause workflows to skip required steps or enter invalid states.

From the tool's definition 'Jump to the specified step within an assignment' — triggers navigation/execution of a workflow step within a Pega assignment

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

POLICY

How to control jump_to_step

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jump_to_step": {
      "limits": [
        {
          "counter": "jump_to_step_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

jump_to_step stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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.

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

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Pega DX MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about jump_to_step

What does the jump_to_step tool do? +

Jump to the specified step within an assignment\. It is categorised as a Execute tool in the Pega DX MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on jump_to_step? +

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

jump_to_step is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit jump_to_step? +

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

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

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