Get a comprehensive list of all attachments associated with a specific Pega case. Retrieves attachment metadata including file details, URLs, creation information, and available actions (download, edit, delete) for each attachment. Only attachments from categories selected in the Attachment Categ...
AI agents call get_case_attachments to retrieve information from Pega DX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval operations only. It queries case attachments and returns metadata including file details, URLs, and creation information. While it mentions available actions like download, edit, and delete, the tool itself does not perform these operations - it only presents them as available. No data is created, modified, deleted, or financial transactions occur.
From the tool's definition Tool description states it 'retrieves' and 'Get a comprehensive list of all attachments' - core function is querying and retrieving metadata with no modification, creation, or deletion of data.
Documented attack patterns abuse exactly the kind of access get_case_attachments 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 get_case_attachments:
{
"version": "1",
"default": "deny",
"tools": {
"get_case_attachments": {}
}
}get_case_attachments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a comprehensive list of all attachments associated with a specific Pega case. Retrieves attachment metadata including file details, URLs, creation information, and available actions (download, edit, delete) for each attachment. Only attachments from categories selected in the Attachment Category rule are returned. Supports optional thumbnail retrieval for image attachments (gif, jpg, jpeg, png, and others) as base64 encoded strings. It is categorised as a Read tool in the Pega DX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pega DX MCP Server MCP server in PolicyLayer and add a rule for get_case_attachments: 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.
get_case_attachments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_case_attachments 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 get_case_attachments. 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.
get_case_attachments 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.