AI agents use add_case_tags 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.
The tool creates or modifies case metadata (tags) within the Pega Platform. This is a Write operation because it involves adding data attributes to an existing case, not reading data, executing arbitrary logic, deleting records, or handling financial transactions.
From the tool's definition add_case_tags - the verb "add" and "tags" indicate creating or modifying metadata on a case object. This is a reversible modification operation (tags can be removed or changed later).
Documented attack patterns abuse exactly the kind of access add_case_tags 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 add_case_tags:
{
"version": "1",
"default": "deny",
"tools": {
"add_case_tags": {
"limits": [
{
"counter": "add_case_tags_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_case_tags 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.
Add multiple tags to a case. 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 add_case_tags: 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.
add_case_tags 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 add_case_tags 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 add_case_tags. 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.
add_case_tags 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.