esm_guidance · Awslabs Valkey MCP: Risk & Policy

WHAT IT DOES

What esm_guidance does on Awslabs Valkey

AI agents use esm_guidance 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 esm_guidance needs a policy

This tool creates and configures AWS infrastructure components (Kafka clusters, Kinesis streams, DynamoDB streams, SQS queues, VPCs, security groups, IAM roles, Event Source Mappings) and generates SAM templates for deployment. This is a Write/provisioning operation with high severity because misuse could spin up significant cloud infrastructure with associated costs and security implications.

From the tool's definition Create and configure AWS infrastructure...Sets up VPCs, security groups, IAM roles, and Event Source Mappings. Generates complete SAM templates for deployment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

esm_guidance Rate-limited

esm_guidance 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": {
    "esm_guidance": {
      "limits": [
        {
          "counter": "esm_guidance_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 esm_guidance

What does the esm_guidance tool do? +

Create and configure AWS infrastructure for streaming data processing. Handles Kafka clusters (MSK), Kinesis streams, DynamoDB streams, SQS queues with Lambda functions. Sets up VPCs, security groups, IAM roles, and Event Source Mappings. Generates complete SAM templates for deployment. 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 esm_guidance? +

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

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

Can I rate-limit esm_guidance? +

Yes. Add a rate_limit block to the esm_guidance 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 esm_guidance completely? +

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

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