update_data_record_full

THE RISK

Medium Risk

Why update_data_record_full needs a policy

This tool creates or modifies data in a reversible manner. While it performs a full override (which is thorough), the operation is still a Write action—the data record can be read, and a subsequent update could restore or change it. It is not Destructive because deletion is not occurring.

From the tool's definition Tool description states: 'Fully update an existing data record' and 'Overrides the entire data record with the provided data object.' The use of 'update' and 'overrides' indicates modification of existing data.

Risk signalsBulk/mass operation — affects multiple targets

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

POLICY

How to control update_data_record_full

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_data_record_full": {
      "limits": [
        {
          "counter": "update_data_record_full_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update_data_record_full 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.

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.

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 →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_data_record_full

What does the update_data_record_full tool do? +

Fully update an existing data record based on conditional save plan configured for a savable Data Page. Overrides the entire data record with the provided data object. 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.

How do I enforce a policy on update_data_record_full? +

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

update_data_record_full is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_data_record_full? +

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

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

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