Medium Risk

copy_image_set

copy_image_set

How to control copy_image_set ↓

What copy_image_set does on Prometheus MCP Server

AI agents use copy_image_set to create or update resources in Prometheus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Prometheus MCP Server environment.

Medium Risk

Why copy_image_set needs a policy

The name 'copy_image_set' suggests creating a copy of an image set, which is a Write operation (creating new data). However, the empty description significantly lowers confidence. It could be a medical imaging operation (e.g., AWS HealthImaging) rather than Prometheus-related.

From the tool's definition Tool name: copy_image_set — description is empty/uninformative

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

How to control copy_image_set

PolicyLayer is an MCP gateway — it sits between your AI agents and Prometheus MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for copy_image_set:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "copy_image_set": {
      "limits": [
        {
          "counter": "copy_image_set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Prometheus 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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about copy_image_set

What does the copy_image_set tool do? +

copy_image_set. It is categorised as a Write tool in the Prometheus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on copy_image_set? +

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

What risk level is copy_image_set? +

copy_image_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit copy_image_set? +

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

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

copy_image_set is provided by the Prometheus MCP Server MCP server (awslabs.prometheus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Prometheus MCP Server tool call.

Start from Prometheus 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.

805 Prometheus 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.