AI agents call sam_logs 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.
Based on the naming convention, 'sam_logs' most likely retrieves or queries logs (Read category). The empty description reduces confidence, but the pattern of sibling tools (many query/analyze functions) and the context of a Prometheus/AWS monitoring server suggests this tool retrieves log data without modification.
From the tool's definition Tool name 'sam_logs' suggests log retrieval functionality. The description is empty, limiting certainty.
Documented attack patterns abuse exactly the kind of access sam_logs 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 sam_logs:
{
"version": "1",
"default": "deny",
"tools": {
"sam_logs": {}
}
}sam_logs 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.
sam_logs. 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 sam_logs: 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.
sam_logs 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 sam_logs 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 sam_logs. 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.
sam_logs 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.