display_generated_image · MCP-Claude MCP: Risk & Policy

WHAT IT DOES

What display_generated_image does on MCP-Claude

AI agents invoke display_generated_image to trigger actions in MCP-Claude. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why display_generated_image needs a policy

Opening a new browser tab is an external operation that causes a side effect in the user's browser environment. It is not purely a read (it has a visible side effect), and it qualifies as an Execute action since it triggers a browser operation. Misuse could be used to open unwanted tabs or expose generated content unexpectedly, but the blast radius is moderate.

From the tool's definition 'display the generated image in a new tab' — triggers an external browser action (opening a new tab)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

display_generated_image Rate-limited

display_generated_image stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "display_generated_image": {
      "limits": [
        {
          "counter": "display_generated_image_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP-Claude, so you can run agents against it safely.

FAQ

Questions about display_generated_image

What does the display_generated_image tool do? +

This function will display the generated image in a new tab. It is categorised as a Execute tool in the MCP-Claude MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on display_generated_image? +

Register the MCP-Claude MCP server in PolicyLayer and add a rule for display_generated_image: 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 MCP-Claude. Nothing to install.

What risk level is display_generated_image? +

display_generated_image is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit display_generated_image? +

Yes. Add a rate_limit block to the display_generated_image 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 display_generated_image completely? +

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

display_generated_image is provided by the MCP-Claude MCP server (virajsamarasinghe/mcp-claude). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

display_generated_image is one line of MCP-Claude's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →