Critical Risk →

untag_resource

Remove tags from a resource.

Part of the AWS HealthImaging MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents may call untag_resource to permanently remove or destroy resources in AWS HealthImaging MCP Server. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call untag_resource in a loop, permanently destroying resources in AWS HealthImaging MCP Server. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

aws-healthimaging-mcp-server.yaml
tools:
  untag_resource:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full AWS HealthImaging MCP Server policy for all 39 tools.

Tool Name untag_resource
Category Destructive
Risk Level Critical

View all 39 tools →

Agents calling destructive-class tools like untag_resource have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

untag_resource is one of the critical-risk operations in AWS HealthImaging MCP Server. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the untag_resource tool do? +

Remove tags from a resource.. It is categorised as a Destructive tool in the AWS HealthImaging 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 untag_resource? +

Add a rule in your Intercept YAML policy under the tools section for untag_resource. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS HealthImaging MCP Server MCP server.

What risk level is untag_resource? +

untag_resource 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 untag_resource? +

Yes. Add a rate_limit block to the untag_resource rule in your Intercept 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 untag_resource completely? +

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

What MCP server provides untag_resource? +

untag_resource is provided by the AWS HealthImaging MCP Server MCP server (awslabs.healthimaging-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.