Deploys a serverless application onto AWS Cloud using AWS SAM (Serverless Application Model) CLI and CloudFormation. Requirements: - AWS SAM CLI MUST be installed and configured in your environment - SAM project MUST be initialized using sam_init tool and built with sam_build. This command depl...
High parameter count (15 properties)
Part of the AWS Serverless MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke sam_deploy to trigger processes or run actions in AWS Serverless MCP Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
sam_deploy can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
sam_deploy:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full AWS Serverless MCP Server policy for all 32 tools.
Agents calling execute-class tools like sam_deploy have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
sam_deploy is one of the high-risk operations in AWS Serverless MCP Server. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Deploys a serverless application onto AWS Cloud using AWS SAM (Serverless Application Model) CLI and CloudFormation. Requirements: - AWS SAM CLI MUST be installed and configured in your environment - SAM project MUST be initialized using sam_init tool and built with sam_build. This command deploys your SAM application's build artifacts located in the .aws-sam directory to AWS Cloud using AWS CloudFormation. The only required parameter is project_directory. SAM will automatically create a S3 bucket where build artifacts are uploaded and referenced by the SAM template. Usage tips: - When you make changes to your application's original files, run sam build to update the .aws-sam directory before deploying. Returns: Dict: SAM deploy command output. It is categorised as a Execute tool in the AWS Serverless MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for sam_deploy. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Serverless MCP Server MCP server.
sam_deploy 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_deploy rule in your Intercept 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 Intercept policy for sam_deploy. 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_deploy is provided by the AWS Serverless MCP Server MCP server (awslabs.aws-serverless-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.