Critical Risk →

policy_engine_delete

policy_engine_delete

How to control policy_engine_delete ↓

What policy_engine_delete does on AWS Pricing MCP Server

AI agents call policy_engine_delete to permanently remove resources in AWS Pricing MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why policy_engine_delete needs a policy

The tool name 'policy_engine_delete' indicates irreversible deletion of policy engine configurations or policies. Even without description details, 'delete' operations are categorized as Destructive per the classification rules. In an AWS context, deleting policies could disable access controls or security configurations, creating a high-severity blast radius if triggered inappropriately by an AI agent.

From the tool's definition Tool name contains 'delete' which is explicitly listed as a destructive operation. Description is empty, limiting full confidence assessment.

Documented attack patterns abuse exactly the kind of access policy_engine_delete gives an agent:

How to control policy_engine_delete

PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Pricing MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for policy_engine_delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "policy_engine_delete"
  ]
}

policy_engine_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register AWS Pricing MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about policy_engine_delete

What does the policy_engine_delete tool do? +

policy_engine_delete. It is categorised as a Destructive tool in the AWS Pricing MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on policy_engine_delete? +

Register the AWS Pricing MCP Server MCP server in PolicyLayer and add a rule for policy_engine_delete: 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 Pricing MCP Server. Nothing to install.

What risk level is policy_engine_delete? +

policy_engine_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit policy_engine_delete? +

Yes. Add a rate_limit block to the policy_engine_delete 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.

How do I block policy_engine_delete completely? +

Set action: deny in the PolicyLayer policy for policy_engine_delete. 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.

What MCP server provides policy_engine_delete? +

policy_engine_delete is provided by the AWS Pricing MCP Server MCP server (awslabs.aws-pricing-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AWS Pricing MCP Server tool call.

Start from AWS Pricing 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 Pricing MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.