Low Risk

describe_supported_languages

describe_supported_languages

How to control describe_supported_languages ↓

What describe_supported_languages does on Prometheus MCP Server

AI agents call describe_supported_languages 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 describe_supported_languages needs a policy

The tool name pattern 'describe_*' is a standard AWS API convention for read-only operations that retrieve configuration or status information. With an empty description, we rely on the name semantics. This operation has no side effects, does not execute code or external operations, and does not modify data. The scope is narrowly informational, making it low-severity if misused.

From the tool's definition Tool name 'describe_supported_languages' indicates a query/retrieval operation that returns metadata about supported languages without modifying state.

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

How to control describe_supported_languages

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

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

describe_supported_languages 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 describe_supported_languages

What does the describe_supported_languages tool do? +

describe_supported_languages. 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 describe_supported_languages? +

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

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

Can I rate-limit describe_supported_languages? +

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

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

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