Get information about the Prometheus server configuration. ## Usage - Use this tool to retrieve the current server configuration - Returns details about the Prometheus URL, AWS region, profile, and service name - Useful for debugging connection issues - If workspace_id is not known, use GetAvail...
Part of the Prometheus MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call GetServerInfo to retrieve information from Prometheus MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though GetServerInfo only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
GetServerInfo:
rules:
- action: allowSee the full Prometheus MCP Server policy for all 5 tools.
Agents calling read-class tools like GetServerInfo have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get information about the Prometheus server configuration. ## Usage - Use this tool to retrieve the current server configuration - Returns details about the Prometheus URL, AWS region, profile, and service name - Useful for debugging connection issues - If workspace_id is not known, use GetAvailableWorkspaces tool first to find available workspaces and ASK THE USER to choose one - Uses DescribeWorkspace API to get the exact workspace URL - No manual URL construction is performed ## Example Input: workspace_id: "ws-12345678-abcd-1234-efgh-123456789012" region: "us-east-1" Output: { "prometheus_url": "https://aps-workspaces.us-east-1.amazonaws.com/workspaces/ws-12345678-abcd-1234-efgh-123456789012", "aws_region": "us-east-1", "aws_profile": "default", "service_name": "aps" }. It is categorised as a Read tool in the Prometheus MCP Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for GetServerInfo. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Prometheus MCP Server MCP server.
GetServerInfo is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the GetServerInfo rule in your Intercept 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.
Set action: deny in the Intercept policy for GetServerInfo. 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.
GetServerInfo is provided by the Prometheus MCP Server MCP server (awslabs.prometheus-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.