remove_instance_from_image_set
AI agents call remove_instance_from_image_set to permanently remove resources in Awslabs Valkey — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The word 'remove' in the tool name implies deletion or detachment of an instance from an image set. This is likely a destructive or write operation. However, the description is empty, which lowers confidence. 'Remove' operations are typically irreversible (the instance is no longer part of the set), so Destructive is the most appropriate category, though it could be Write if the instance remains elsewhere.
From the tool's definition Tool name 'remove_instance_from_image_set' suggests removing/deleting an instance from an image set, which is likely irreversible.
Attacks that exploit this kind of access
remove_instance_from_image_set. It is categorised as a Destructive tool in the Awslabs Valkey MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for remove_instance_from_image_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 Awslabs Valkey. Nothing to install.
remove_instance_from_image_set is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_instance_from_image_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 remove_instance_from_image_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.
remove_instance_from_image_set is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.