AI agents call list_change_sets to retrieve information from Sceptre without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates change sets without creating, modifying, deleting, or executing any operations. It has no side effects on infrastructure or data state. The blast radius of misuse is minimal—an agent could only gain visibility into existing change sets, not alter them or trigger deployments.
From the tool's definition Tool name is 'list_change_sets' and description states 'List all change sets for a CloudFormation stack via Sceptre.' The verb 'list' and the operation of retrieving/querying existing change sets with no modification capability indicates a read-only action.
Attacks that exploit this kind of access
List all change sets for a CloudFormation stack via Sceptre. It is categorised as a Read tool in the Sceptre MCP Server, which means it retrieves data without modifying state.
Register the Sceptre MCP server in PolicyLayer and add a rule for list_change_sets: 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.
list_change_sets is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_change_sets 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 list_change_sets. 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.
list_change_sets 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →