Upload a file to Pega as a temporary attachment that can later be linked to cases. Creates a temporary attachment instance that auto-expires after 2 hours if not linked. Supports multiple input methods for cross-client compatibility.
AI agents use upload_attachment 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 a new temporary attachment resource in Pega, which is a reversible write operation. While it modifies system state by adding data, the attachment auto-expires after 2 hours if not linked, making it inherently temporary and non-destructive.
From the tool's definition Tool description explicitly states 'Upload a file to Pega' and 'Creates a temporary attachment instance', indicating data creation/modification via file upload.
Documented attack patterns abuse exactly the kind of access upload_attachment 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 upload_attachment:
{
"version": "1",
"default": "deny",
"tools": {
"upload_attachment": {
"limits": [
{
"counter": "upload_attachment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}upload_attachment 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.
Upload a file to Pega as a temporary attachment that can later be linked to cases. Creates a temporary attachment instance that auto-expires after 2 hours if not linked. Supports multiple input methods for cross-client compatibility. 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 upload_attachment: 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.
upload_attachment 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 upload_attachment 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 upload_attachment. 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.
upload_attachment 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.