sam_logs
AI agents call sam_logs to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the name alone, 'sam_logs' appears to retrieve AWS SAM (Serverless Application Model) logs, a read operation with no side effects. However, the empty description significantly reduces confidence. The tool is classified as Read because log retrieval is fundamentally a query operation, though severity is marked low due to the ambiguity and the need for confirmation of actual functionality.
From the tool's definition Tool name is 'sam_logs' which suggests retrieving or querying log data, consistent with read operations. Description is empty, which limits confidence in the classification.
Attacks that exploit this kind of access
sam_logs. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey 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 Awslabs Valkey. 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 Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.