AI agents call delete_app to permanently remove resources in AWS Labs Timestream for InfluxDB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion operations are irreversible and fall into the Destructive category. In an AWS Timestream context, deleting an app likely removes a configured application and associated metadata permanently. Without a description, confidence is moderate, but the destructive intent of the name is clear. Severity is high because unintended deletion of applications could disrupt monitoring pipelines or data collection systems.
From the tool's definition Tool name 'delete_app' indicates deletion of an application resource. Description is empty, which limits certainty, but the verb 'delete' conventionally signals irreversible removal of data or infrastructure.
Documented attack patterns abuse exactly the kind of access delete_app gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Labs Timestream for InfluxDB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_app:
{
"version": "1",
"default": "deny",
"hide": [
"delete_app"
]
} delete_app 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.
delete_app. It is categorised as a Destructive tool in the AWS Labs Timestream for InfluxDB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS Labs Timestream for InfluxDB MCP Server MCP server in PolicyLayer and add a rule for delete_app: 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 Labs Timestream for InfluxDB MCP Server. Nothing to install.
delete_app 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 delete_app 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 delete_app. 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.
delete_app is provided by the AWS Labs Timestream for InfluxDB MCP Server MCP server (awslabs.timestream-for-influxdb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Labs Timestream for InfluxDB 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 Labs Timestream for InfluxDB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.