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.
AI agents invoke esm_guidance to trigger actions in AWS Support MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool creates and configures real AWS infrastructure components (Kafka/MSK clusters, Kinesis streams, DynamoDB streams, SQS queues, VPCs, security groups, IAM roles, Lambda Event Source Mappings) and generates SAM templates for deployment. It goes beyond merely writing config — it provisions live cloud infrastructure and triggers deployment pipelines, making it Execute-level.
From the tool's definition Create and configure AWS infrastructure for streaming data processing... Sets up VPCs, security groups, IAM roles, and Event Source Mappings. Generates complete SAM templates for deployment.
Documented attack patterns abuse exactly the kind of access esm_guidance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Support MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for esm_guidance:
{
"version": "1",
"default": "deny",
"tools": {
"esm_guidance": {
"limits": [
{
"counter": "esm_guidance_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}esm_guidance stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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 Execute tool in the AWS Support MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS Support MCP Server 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 AWS Support MCP Server. Nothing to install.
esm_guidance is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
esm_guidance is provided by the AWS Support MCP Server MCP server (awslabs.aws-support-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Support MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 AWS Support MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.