This record as markdown: /tools/quangdang46-uefn-verse-mcp/tag-add.md
What tag_add does on Uefn
AI agents use tag_add to create or update resources in Uefn, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Uefn environment.
Why tag_add is rated Medium
Tag addition in a game editor is a reversible Write operation that creates or modifies metadata. The lack of description lowers confidence, but the naming convention and context of editor operations (with sibling Write tools like actor_set_label) suggests it modifies state without deletion or execution of arbitrary code.
From the tool's definition Tool name 'tag_add' indicates adding/creating tags in the UEFN editor context. No description provided to clarify exact behavior, but sibling tools show patterns of actor manipulation (actor_set_label, actor_move_to_folder) suggesting this modifies metadata…
Attacks that exploit this kind of access
The rule that runs tag_add 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_add, this is the rule to start with:
tag_add stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Uefn, apply this rule, and every tag_add call is checked against it from then on.
Questions about tag_add
tag_add is a write tool on the Uefn MCP server. It is categorised as a Write tool in the Uefn MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Uefn MCP server in PolicyLayer and add a rule for tag_add: 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.
tag_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the tag_add 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 tag_add. 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.
tag_add 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.
More on Uefn, and thousands of servers like it.
This server
Across the catalogue