Low Risk

get_language_metrics

get_language_metrics

How to control get_language_metrics ↓

What get_language_metrics does on Prometheus MCP Server

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

Low Risk

Why get_language_metrics needs a policy

The tool name and server context suggest this retrieves metrics data from Prometheus without modifying state. No side effects, destructive operations, or external triggers are implied. This is a straightforward data retrieval operation, classified as Read with low severity due to its passive nature.

From the tool's definition Tool name 'get_language_metrics' combined with server description 'MCP server for interacting with AWS Managed Prometheus' indicates metric retrieval. The prefix 'get_' is characteristic of read operations. Description is empty, limiting full confidence.

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

How to control get_language_metrics

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

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

get_language_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 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_language_metrics

What does the get_language_metrics tool do? +

get_language_metrics. It is categorised as a Read tool in the Prometheus MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_language_metrics? +

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

What risk level is get_language_metrics? +

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

Can I rate-limit get_language_metrics? +

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

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

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