Deletes a Timestream for InfluxDB DB instance by the instance-identifier
AI agents call DeleteDbInstance to permanently remove resources in Amazon ECS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a database instance, which is an irreversible operation that destroys all data stored in that instance. This is the most severe category (Destructive) because deletion cannot be undone and represents total loss of a data store. The blast radius is critical—an agent could accidentally or maliciously destroy production databases.
From the tool's definition Tool name is 'DeleteDbInstance' and description states it 'Deletes a Timestream for InfluxDB DB instance by the instance-identifier'. The word 'Deletes' combined with a database instance as the target indicates irreversible removal of data and infrastructure.
Documented attack patterns abuse exactly the kind of access DeleteDbInstance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon ECS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for DeleteDbInstance:
{
"version": "1",
"default": "deny",
"hide": [
"DeleteDbInstance"
]
}DeleteDbInstance 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.
Deletes a Timestream for InfluxDB DB instance by the instance-identifier. It is categorised as a Destructive tool in the Amazon ECS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Amazon ECS MCP Server MCP server in PolicyLayer and add a rule for DeleteDbInstance: 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 Amazon ECS MCP Server. Nothing to install.
DeleteDbInstance 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 DeleteDbInstance 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 DeleteDbInstance. 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.
DeleteDbInstance is provided by the Amazon ECS MCP Server MCP server (awslabs.ecs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon ECS 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 Amazon ECS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.