create-log-group
AI agents use create-log-group to create or update resources in Awslabs Valkey — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Awslabs Valkey environment.
This tool creates a new CloudWatch Log Group, which is a reversible write operation that establishes a new resource in AWS. It does not delete data (not Destructive), execute arbitrary code (not Execute), nor involve financial transactions (not Financial). The confidence is reduced to 0.75 rather than higher because the description is empty, leaving some ambiguity about exact behavior.
From the tool's definition Tool name 'create-log-group' indicates creation of a new CloudWatch Log Group resource. The prefix 'create-' combined with 'log-group' suggests this tool creates or provisions a new logging destination, which is a write operation that modifies AWS…
Attacks that exploit this kind of access
create-log-group. It is categorised as a Write tool in the Awslabs Valkey MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for create-log-group: 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.
create-log-group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create-log-group 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 create-log-group. 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.
create-log-group 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.