Medium Risk

collections_create

Create a new collection.

Part of the Prometheus MCP server.

collections_create can modify Prometheus MCP data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE PROMETHEUS MCP →

Free to start. No card required.

AI agents use collections_create to create or modify resources in Prometheus MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call collections_create repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Prometheus MCP.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

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

See the full Prometheus MCP policy for all 12 tools.

Get this rule live on your own Prometheus MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY PROMETHEUS MCP →

View all 12 tools →

These attack patterns abuse exactly the kind of access collections_create gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so collections_create only ever does what you allow.

SECURE PROMETHEUS MCP →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the collections_create tool do? +

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

How do I enforce a policy on collections_create? +

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

What risk level is collections_create? +

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

Can I rate-limit collections_create? +

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

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

collections_create is provided by the Prometheus MCP server (https://mcp.prometheus.sv/). 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 tool call.

Deterministic rules across all 12 Prometheus MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.