AI agents call describe_change_set 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.
The 'describe_' prefix is a standard AWS API pattern for read-only operations that retrieve resource metadata and state. Describing a change set returns information about planned infrastructure changes without executing or applying them. This is a query operation with no side effects, fitting the Read category. Severity is low because misuse would only expose information, not cause infrastructure changes.
From the tool's definition Tool name 'describe_change_set' indicates a retrieval operation. Naming convention 'describe_*' paired with sibling 'create_change_set' and 'delete_change_set' strongly suggests this retrieves metadata about a CloudFormation change set without modifying it.
Attacks that exploit this kind of access
describe_change_set. 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 describe_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.
describe_change_set 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 describe_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.
Set action: deny in the PolicyLayer policy for describe_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.
describe_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.
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 →