AI agents call get_config_check_operation 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.
The 'get_' prefix conventionally denotes read-only data retrieval. Although the description is empty (reducing confidence), the naming pattern and Prometheus context (a monitoring system) indicate this likely queries configuration or check operation state without modifying data. No evidence suggests write, destructive, or financial operations.
From the tool's definition Tool name 'get_config_check_operation' with a 'get' prefix indicates data retrieval. The context of AWS Managed Prometheus and sibling tools like 'aggregate' and 'analyze_*' functions suggest this retrieves configuration or operational status data.
Documented attack patterns abuse exactly the kind of access get_config_check_operation gives an agent:
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_config_check_operation:
{
"version": "1",
"default": "deny",
"tools": {
"get_config_check_operation": {}
}
}get_config_check_operation is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_config_check_operation. It is categorised as a Read tool in the Prometheus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for get_config_check_operation: 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.
get_config_check_operation 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 get_config_check_operation 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.
Set action: deny in the PolicyLayer policy for get_config_check_operation. 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.
get_config_check_operation 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.
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.