create_change_set · Sceptre MCP: Risk & Policy

WHAT IT DOES

What create_change_set does on Sceptre

AI agents use create_change_set to create or update resources in Sceptre — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sceptre environment.

WHY IT NEEDS A POLICY

Why create_change_set needs a policy

Creating a CloudFormation change set is a Write operation: it generates a proposed set of changes to a stack but does not execute them. It is reversible (change sets can be deleted without applying). Severity is medium because it modifies CloudFormation state and could be a precursor to destructive infrastructure changes, but by itself does not apply or destroy anything.

From the tool's definition Tool name: 'create_change_set' — in the context of a Sceptre CloudFormation management MCP server, a change set is a preview of proposed infrastructure changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_change_set Rate-limited

create_change_set 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": {
    "create_change_set": {
      "limits": [
        {
          "counter": "create_change_set_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 Sceptre, so you can run agents against it safely.

FAQ

Questions about create_change_set

What does the create_change_set tool do? +

create_change_set. It is categorised as a Write tool in the Sceptre MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_change_set? +

Register the Sceptre MCP server in PolicyLayer and add a rule for create_change_set: 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 Sceptre. Nothing to install.

What risk level is create_change_set? +

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

Can I rate-limit create_change_set? +

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

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

create_change_set is provided by the Sceptre MCP server (sceptre/sceptre-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.