CreateAHOSequenceStore
AI agents use CreateAHOSequenceStore 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.
The tool name indicates it creates a sequence store, which is a write operation that generates new persistent data structures. While the description is empty (lowering confidence), the semantic meaning of 'Create' combined with 'SequenceStore' indicates a Write action.
From the tool's definition Tool name 'CreateAHOSequenceStore' indicates creation of a data structure (AHO Sequence Store). The 'Create' prefix strongly suggests a Write operation that establishes new resources.
Attacks that exploit this kind of access
CreateAHOSequenceStore. 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 CreateAHOSequenceStore: 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.
CreateAHOSequenceStore 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 CreateAHOSequenceStore 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 CreateAHOSequenceStore. 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.
CreateAHOSequenceStore 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.