remove_instance_from_image_set
AI agents call remove_instance_from_image_set to permanently remove resources in AWS S3 Tables MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name implies removing/deleting an element from a collection. 'Remove' operations are typically destructive (irreversible deletion or detachment). However, the description is empty, which lowers confidence. Given the naming pattern and context of an AWS S3 Tables MCP server dealing with image sets, this is likely a destructive operation that cannot be undone.
From the tool's definition Tool name: 'remove_instance_from_image_set' — 'remove' suggests deletion or detachment of an instance from an image set, which may be irreversible.
Documented attack patterns abuse exactly the kind of access remove_instance_from_image_set gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS S3 Tables MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_instance_from_image_set:
{
"version": "1",
"default": "deny",
"hide": [
"remove_instance_from_image_set"
]
} remove_instance_from_image_set disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
remove_instance_from_image_set. It is categorised as a Destructive tool in the AWS S3 Tables MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS S3 Tables MCP Server 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 AWS S3 Tables MCP Server. 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 AWS S3 Tables MCP Server MCP server (awslabs.s3-tables-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS S3 Tables MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 AWS S3 Tables MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.