AI agents call get_config_check_summary 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 and 'summary' suffix strongly suggest this tool retrieves or queries configuration check data, placing it in the Read category. However, confidence is moderate (0.7) because the description is empty, preventing verification of whether this tool might have side effects. In the context of AWS Managed Prometheus, config checks are typically diagnostic/monitoring queries.
From the tool's definition Tool name 'get_config_check_summary' indicates retrieval of configuration check summary data. Prefix 'get_' is characteristic of read operations that retrieve or query information without modification.
Documented attack patterns abuse exactly the kind of access get_config_check_summary 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_summary:
{
"version": "1",
"default": "deny",
"tools": {
"get_config_check_summary": {}
}
}get_config_check_summary 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_summary. 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_summary: 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_summary 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_summary 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_summary. 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_summary 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.