Retrieve the list of attachment categories available for a specific Pega case, filtered by attachment type (File or URL). Returns category metadata including user permissions (view, create, edit, delete) for each attachment category associated with the case type. The API uses the class name from ...
AI agents call get_attachment_categories 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 is a read-only operation that queries Pega Platform for attachment category metadata and associated permissions. It has no side effects—it does not create, modify, delete, or execute any operations. The inclusion of permission metadata in the response is informational only and does not grant permissions or enable any write/execute/destructive actions.
From the tool's definition Tool retrieves metadata about attachment categories and user permissions; no modifications, deletions, or external operations. Described as "Retrieve the list of attachment categories" and "Returns category metadata including user permissions".
Documented attack patterns abuse exactly the kind of access get_attachment_categories 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_attachment_categories:
{
"version": "1",
"default": "deny",
"tools": {
"get_attachment_categories": {}
}
}get_attachment_categories 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.
Retrieve the list of attachment categories available for a specific Pega case, filtered by attachment type (File or URL). Returns category metadata including user permissions (view, create, edit, delete) for each attachment category associated with the case type. The API uses the class name from the caseID to get attachment categories and filters them based on the type parameter. Only attachment categories configured in the Attachment Category rule are returned. Useful for understanding what attachment categories are available and what operations the current user can perform on each category. 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_attachment_categories: 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_attachment_categories 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_attachment_categories 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_attachment_categories. 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_attachment_categories 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.