Critical Risk →

remove-tag-from-entity

Remove a tag from an entity

Removes classification metadata

Part of the Confluent Kafka MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents may call remove-tag-from-entity to permanently remove or destroy resources in Confluent Kafka. 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 remove-tag-from-entity in a loop, permanently destroying resources in Confluent Kafka. 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.

confluent-kafka.yaml
tools:
  remove-tag-from-entity:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Confluent Kafka policy for all 46 tools.

Tool Name remove-tag-from-entity
Category Destructive
Risk Level Critical

View all 46 tools →

Agents calling destructive-class tools like remove-tag-from-entity 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.

remove-tag-from-entity is one of the critical-risk operations in Confluent Kafka. 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 remove-tag-from-entity tool do? +

Remove a tag from an entity. It is categorised as a Destructive tool in the Confluent Kafka 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 remove-tag-from-entity? +

Add a rule in your Intercept YAML policy under the tools section for remove-tag-from-entity. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Confluent Kafka MCP server.

What risk level is remove-tag-from-entity? +

remove-tag-from-entity 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 remove-tag-from-entity? +

Yes. Add a rate_limit block to the remove-tag-from-entity 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 remove-tag-from-entity completely? +

Set action: deny in the Intercept policy for remove-tag-from-entity. 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 remove-tag-from-entity? +

remove-tag-from-entity is provided by the Confluent Kafka MCP server (@@confluentinc/mcp-confluent). 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.

Currently onboarding teams running MCP in production.
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.

// REQUEST EARLY ACCESS

We're letting people in as fast as we can.

You're in the queue.

We'll be in touch as soon as we can let you in.