sam_deploy · AWS IoT SiteWise MCP Server MCP: Risk & Policy

WHAT IT DOES

What sam_deploy does on AWS IoT SiteWise MCP Server

AI agents invoke sam_deploy to trigger actions in AWS IoT SiteWise 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.

WHY IT NEEDS A POLICY

Why sam_deploy needs a policy

SAM deployments are Execute operations because they trigger automated infrastructure provisioning workflows whose effects depend on deployment configuration arguments. This differs from Write (reversible modifications) because deployments have cascading effects across multiple AWS services and resources.

From the tool's definition Tool name 'sam_deploy' indicates AWS Serverless Application Model deployment functionality. SAM deployments execute infrastructure-as-code operations that provision, update, and configure AWS resources.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sam_deploy Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sam_deploy": {
      "limits": [
        {
          "counter": "sam_deploy_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about sam_deploy

What does the sam_deploy tool do? +

sam_deploy. It is categorised as a Execute tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sam_deploy? +

Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for sam_deploy: 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 IoT SiteWise MCP Server. Nothing to install.

What risk level is sam_deploy? +

sam_deploy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sam_deploy? +

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

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

What MCP server provides sam_deploy? +

sam_deploy is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.