List all available Prometheus workspaces in the specified region. ## Usage - Use this tool to see all available Prometheus workspaces - Shows workspace ID, alias, status, and URL for active workspaces - IMPORTANT: When multiple workspaces are available, present them to the user and ask them to c...
Part of the Prometheus MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call GetAvailableWorkspaces 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 GetAvailableWorkspaces 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:
GetAvailableWorkspaces:
rules:
- action: allowSee the full Prometheus MCP Server policy for all 5 tools.
Agents calling read-class tools like GetAvailableWorkspaces 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.
List all available Prometheus workspaces in the specified region. ## Usage - Use this tool to see all available Prometheus workspaces - Shows workspace ID, alias, status, and URL for active workspaces - IMPORTANT: When multiple workspaces are available, present them to the user and ask them to choose one - DO NOT automatically select a workspace; always ask the user to choose when multiple options exist - Uses DescribeWorkspace API to get the exact URL for each workspace - No manual URL construction is performed ## Example Input: region: "us-east-1" Output: { "workspaces": [ { "workspace_id": "ws-12345678-abcd-1234-efgh-123456789012", "alias": "production", "status": "ACTIVE", "prometheus_url": "https://aps-workspaces.us-east-1.amazonaws.com/workspaces/ws-12345678-abcd-1234-efgh-123456789012", "is_configured": true }, { "workspace_id": "ws-87654321-dcba-4321-hgfe-210987654321", "alias": "development", "status": "ACTIVE", "prometheus_url": "https://aps-workspaces.us-east-1.amazonaws.com/workspaces/ws-87654321-dcba-4321-hgfe-210987654321", "is_configured": false } ], "count": 2, "region": "us-east-1", "requires_user_selection": true, "configured_workspace_id": "ws-12345678-abcd-1234-efgh-123456789012" }. 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 GetAvailableWorkspaces. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Prometheus MCP Server MCP server.
GetAvailableWorkspaces 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 GetAvailableWorkspaces 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 GetAvailableWorkspaces. 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.
GetAvailableWorkspaces 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.