widget

// WHEN AI AGENTS USE THIS TOOL

AI agents may call widget to permanently remove or destroy resources in Ue. 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.

// WHY ENFORCE A POLICY ON WIDGET

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

// RECOMMENDED POLICY

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

ue.yaml

tools:
  widget:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Ue policy for all 20 tools.

// DETAILS

Tool Name widget

Category Destructive

MCP Server Ue MCP Server

Risk Level Critical

// MORE UE TOOLS

Destructive animation Destructive asset Destructive blueprint Destructive demo Destructive editor Destructive foliage Destructive gameplay Destructive level

View all 20 tools →

// WHAT CAN GO WRONG

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

Browse the full MCP Attack Database →

// OTHER DESTRUCTIVE TOOLS ACROSS MCP SERVERS

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

AbraFlexi contact_delete AbraFlexi evidence_delete AbraFlexi invoice_issued_delete AbraFlexi product_delete Agent Passport System — Cryptographic Identity for AI Agents remove_intent_card Agent Passport System — Cryptographic Identity for AI Agents revoke_delegation

// IN CONTEXT OF CRITICAL RISK

widget is one of the critical-risk operations in Ue. 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.

// RELATED READING

// FAQ

What does the widget tool do? +

UMG Widget Blueprints, Editor Utility Widgets, and Editor Utility Blueprints. Actions: - read_tree: Read widget hierarchy. Params: assetPath - get_details: Inspect widget. Params: assetPath, widgetName - set_property: Set widget property. Params: assetPath, widgetName, propertyName, value - list: List Widget BPs. Params: directory?, recursive? - read_animations: Read UMG animations. Params: assetPath - create: Create Widget BP. Params: name, packagePath?, parentClass? - create_utility_widget: Create editor utility widget. Params: name, packagePath? - run_utility_widget: Open editor utility widget. Params: assetPath - create_utility_blueprint: Create editor utility blueprint. Params: name, packagePath? - run_utility_blueprint: Run editor utility blueprint. Params: assetPath - add_widget: Add widget to widget tree. Params: assetPath, widgetClass, widgetName?, parentWidgetName? - remove_widget: Remove widget from tree. Params: assetPath, widgetName - move_widget: Reparent widget. Params: assetPath, widgetName, newParentWidgetName - list_classes: List available widget classes - list_runtime: (#160) List live UUserWidget instances in the PIE world. Params: classFilter?, namePrefix?, viewportOnly? - get_runtime: (#160) Inspect a live PIE widget tree with text/visibility/brush/percent values. Params: widgetName? | className?, childName?, maxDepth?. It is categorised as a Destructive tool in the Ue 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 widget? +

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

What risk level is widget? +

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

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

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

widget is provided by the Ue MCP server (ue-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Ue