AI agents invoke sam_init to trigger actions in Amazon ECS 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.
The description is empty, lowering confidence. However, 'sam_init' on an AWS ECS MCP server likely invokes the AWS SAM CLI 'sam init' command, which executes external tooling and creates files/directories. This falls under Execute as it triggers external operations. Severity is high because it could scaffold infrastructure-as-code templates that affect cloud deployments.
From the tool's definition Tool name 'sam_init' suggests initializing a SAM (Serverless Application Model) project, which involves running commands and creating project scaffolding on the filesystem.
Documented attack patterns abuse exactly the kind of access sam_init gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon ECS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for sam_init:
{
"version": "1",
"default": "deny",
"tools": {
"sam_init": {
"limits": [
{
"counter": "sam_init_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} sam_init 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.
sam_init. It is categorised as a Execute tool in the Amazon ECS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Amazon ECS MCP Server MCP server in PolicyLayer and add a rule for sam_init: 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 Amazon ECS MCP Server. Nothing to install.
sam_init 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 sam_init 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 sam_init. 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.
sam_init is provided by the Amazon ECS MCP Server MCP server (awslabs.ecs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon ECS 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 Amazon ECS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.