Low Risk

connect

connect

How to control connect ↓

What connect does on Prometheus MCP Server

AI agents call connect as a supporting operation in Prometheus MCP Server workflows.

Low Risk

Why connect needs a policy

The description is empty, making it impossible to reliably classify the tool. The name 'connect' could imply establishing a connection to a Prometheus endpoint (Read-like), but without further evidence, confidence is very low. Defaulting to Other with low severity.

From the tool's definition Tool name is 'connect' but description is empty or uninformative; cannot determine what this tool does based on name alone.

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

How to control connect

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "connect": {
      "limits": [
        {
          "counter": "connect_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

connect gets a rate cap, and 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.
SET A RULE FOR THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about connect

What does the connect tool do? +

connect. It is categorised as a Other tool in the Prometheus MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on connect? +

Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for connect: 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 connect? +

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

Can I rate-limit connect? +

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

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

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