CreateAHOWorkflowVersion · Awslabs Valkey MCP: Risk & Policy

WHAT IT DOES

What CreateAHOWorkflowVersion does on Awslabs Valkey

AI agents use CreateAHOWorkflowVersion 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.

WHY IT NEEDS A POLICY

Why CreateAHOWorkflowVersion needs a policy

The name implies creating/writing a new workflow version resource. This is reversible (can be modified or deleted later), so it is categorized as Write rather than Execute or Destructive. Without a description, confidence is moderate. In an AWS service context, creating workflow versions typically commits a new immutable or deletable artifact, placing it in Write rather than higher severity categories.

From the tool's definition Tool name 'CreateAHOWorkflowVersion' indicates creation of a workflow version, which modifies state. The description is empty, limiting certainty. The verb 'Create' suggests a write operation that adds a new entity rather than executing arbitrary code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

CreateAHOWorkflowVersion Rate-limited

CreateAHOWorkflowVersion stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "CreateAHOWorkflowVersion": {
      "limits": [
        {
          "counter": "createahoworkflowversion_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Awslabs Valkey, so you can run agents against it safely.

FAQ

Questions about CreateAHOWorkflowVersion

What does the CreateAHOWorkflowVersion tool do? +

CreateAHOWorkflowVersion. 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.

How do I enforce a policy on CreateAHOWorkflowVersion? +

Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for CreateAHOWorkflowVersion: 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.

What risk level is CreateAHOWorkflowVersion? +

CreateAHOWorkflowVersion is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit CreateAHOWorkflowVersion? +

Yes. Add a rate_limit block to the CreateAHOWorkflowVersion 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.

How do I block CreateAHOWorkflowVersion completely? +

Set action: deny in the PolicyLayer policy for CreateAHOWorkflowVersion. 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.

What MCP server provides CreateAHOWorkflowVersion? +

CreateAHOWorkflowVersion 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.