Low Risk

get_case_tags

Get list of tags associated to a case

How to control get_case_tags ↓

What get_case_tags does on Pega DX MCP Server

AI agents call get_case_tags 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.

Low Risk

Why get_case_tags needs a policy

This tool performs a simple query to retrieve existing tags on a case. It does not create, modify, delete, or execute any operations. The action is read-only and returns data without altering any state. This is a low-severity operation as retrieving tag metadata poses minimal risk.

From the tool's definition Tool name is 'get_case_tags' and description states 'Get list of tags associated to a case' — this is a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_case_tags gives an agent:

How to control get_case_tags

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_tags:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_case_tags": {}
  }
}

get_case_tags is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Pega DX MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_case_tags

What does the get_case_tags tool do? +

Get list of tags associated to a case. It is categorised as a Read tool in the Pega DX MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_case_tags? +

Register the Pega DX MCP Server MCP server in PolicyLayer and add a rule for get_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.

What risk level is get_case_tags? +

get_case_tags is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_case_tags? +

Yes. Add a rate_limit block to the get_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.

How do I block get_case_tags completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_case_tags? +

get_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.

Enforce policy on every Pega DX MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.