Low Risk

cloud_get_service_metrics

Get Prometheus metrics for a service.

How to control cloud_get_service_metrics ↓

What cloud_get_service_metrics does on MCP ClickHouse

AI agents call cloud_get_service_metrics to retrieve information from MCP ClickHouse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why cloud_get_service_metrics needs a policy

This tool retrieves monitoring metrics (Prometheus data) from a ClickHouse Cloud service. It is a read-only query operation that observes service state without creating, modifying, executing, or deleting anything. The blast radius is minimal—an AI agent misusing this could at most expose performance data already available to authorized users of the service, not cause infrastructure damage or financial impact.

From the tool's definition Tool name is 'cloud_get_service_metrics' and description states 'Get Prometheus metrics for a service' — a retrieval operation with no modification or destructive capability.

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

How to control cloud_get_service_metrics

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

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

cloud_get_service_metrics 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 MCP ClickHouse — 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 cloud_get_service_metrics

What does the cloud_get_service_metrics tool do? +

Get Prometheus metrics for a service. It is categorised as a Read tool in the MCP ClickHouse MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cloud_get_service_metrics? +

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

What risk level is cloud_get_service_metrics? +

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

Can I rate-limit cloud_get_service_metrics? +

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

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

cloud_get_service_metrics is provided by the MCP ClickHouse MCP server (oualib/chmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP ClickHouse tool call.

Start from MCP ClickHouse, 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.

55 MCP ClickHouse 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.