tag_remove

A destructive tool on the Uefn MCP server.

SERVERUefn SOURCEquangdang46/uefn-verse-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/quangdang46-uefn-verse-mcp/tag-remove.md

WHAT IT DOES

What tag_remove does on Uefn

AI agents call tag_remove to permanently remove resources in Uefn, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why tag_remove is rated Critical

The name 'tag_remove' strongly implies removing/deleting a tag from an actor or asset, which is a destructive (irreversible deletion) operation. However, the empty description lowers confidence significantly. In context of a UEFN editor bridge, tag removal is likely a metadata modification that could be reversible (Write), but 'remove' semantics lean Destructive.

From the tool's definition Tool name 'tag_remove' — description is empty and uninformative

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs tag_remove safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Uefn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tag_remove, this is the rule to start with:

tag_remove Hidden

tag_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "tag_remove"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Uefn, apply this rule, and every tag_remove call is checked against it from then on.

FAQ

Questions about tag_remove

What does the tag_remove tool do? +

tag_remove is a destructive tool on the Uefn MCP server. It is categorised as a Destructive tool in the Uefn 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 tag_remove? +

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

What risk level is tag_remove? +

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

Yes. Add a rate_limit block to the tag_remove 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 tag_remove completely? +

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

tag_remove is provided by the Uefn MCP server (quangdang46/uefn-verse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Uefn, and thousands of servers like it.

This server

All 143 Uefn tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →