Save assignment action form data without executing the action. Implements
AI agents use save_assignment_action 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 or modifies assignment action form data in Pega. While it doesn't execute the action itself, it persists form data changes, making it a Write operation. Severity is medium because modifying assignment data could affect workflow state and business processes, but it's reversible (can be updated again) and doesn't execute external operations or delete data.
From the tool's definition save_assignment_action: 'Save assignment action form data' indicates data modification; 'without executing the action' indicates reversible change rather than destructive or Execute category.
Documented attack patterns abuse exactly the kind of access save_assignment_action 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 save_assignment_action:
{
"version": "1",
"default": "deny",
"tools": {
"save_assignment_action": {
"limits": [
{
"counter": "save_assignment_action_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} save_assignment_action 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.
Save assignment action form data without executing the action. Implements. 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 save_assignment_action: 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.
save_assignment_action 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 save_assignment_action 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 save_assignment_action. 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.
save_assignment_action 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.