stream_info

THE RISK

Low Risk

Why stream_info needs a policy

This tool retrieves metadata or status information about a stream in AWS Managed Prometheus. It performs a query/lookup operation with no side effects, reversible modifications, code execution, data destruction, or financial impact. The verb 'Get' and noun 'information' are characteristic of Read operations.

From the tool's definition Tool name 'stream_info' and description 'Get information about stream' indicate a retrieval operation with no modification or execution capability.

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

POLICY

How to control stream_info

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stream_info": {}
  }
}

stream_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Prometheus MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Prometheus MCP Server tools

Destructive bulk_delete_by_criteria bulk_delete_by_criteria Destructive cache_delete Delete a value from the cache. Destructive cache_delete_many Delete multiple values from the cache. Destructive cache_delete_multi Delete multiple values from the cache (alias for delete_many). Destructive delete delete Destructive delete_access_key delete_access_key Destructive delete_agent_runtime delete_agent_runtime Destructive delete_agent_runtime_endpoint delete_agent_runtime_endpoint

All 805 Prometheus MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about stream_info

What does the stream_info tool do? +

Get information about stream. 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 stream_info? +

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

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

Can I rate-limit stream_info? +

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

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

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

CHECK YOUR STACK →