AI agents call delete_resource to permanently remove resources in Amazon Redshift MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The word 'delete' is a strong indicator of destructive operations. Redshift is a data warehouse service where deleted resources (clusters, tables, databases) result in permanent data loss. Even without a description, the naming convention strongly suggests this tool removes resources irreversibly. This warrants Destructive category and high severity due to potential data loss and infrastructure impact.
From the tool's definition Tool name 'delete_resource' with empty description indicates an irreversible deletion operation. In the context of an AWS Redshift server, this likely deletes cluster resources, databases, or other persistent infrastructure that cannot be undone.
Documented attack patterns abuse exactly the kind of access delete_resource gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Redshift MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_resource:
{
"version": "1",
"default": "deny",
"hide": [
"delete_resource"
]
}delete_resource 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_resource. It is categorised as a Destructive tool in the Amazon Redshift MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Amazon Redshift MCP Server MCP server in PolicyLayer and add a rule for delete_resource: 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 Redshift MCP Server. Nothing to install.
delete_resource 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_resource 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_resource. 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_resource is provided by the Amazon Redshift MCP Server MCP server (awslabs.redshift-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon Redshift 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 Redshift MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.