AI agents call QueryKnowledgeBases 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.
Query operations are classified as Read category since they retrieve data without side effects. The empty description reduces confidence slightly, but the semantic intent of 'Query' combined with read-only access patterns typical of knowledge base queries justifies Read classification.
From the tool's definition Tool name 'QueryKnowledgeBases' indicates a query operation on knowledge base data. Description is empty, limiting confidence. However, 'Query' pattern combined with 'KnowledgeBases' suggests data retrieval without modification.
Documented attack patterns abuse exactly the kind of access QueryKnowledgeBases 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 QueryKnowledgeBases:
{
"version": "1",
"default": "deny",
"tools": {
"QueryKnowledgeBases": {}
}
}QueryKnowledgeBases 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.
QueryKnowledgeBases. 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 QueryKnowledgeBases: 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.
QueryKnowledgeBases 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 QueryKnowledgeBases 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 QueryKnowledgeBases. 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.
QueryKnowledgeBases 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.