pcg

// WHEN AI AGENTS USE THIS TOOL

AI agents may call pcg 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 PCG

Without a policy, an AI agent could call pcg 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:
  pcg:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Ue policy for all 20 tools.

// DETAILS

Tool Name pcg

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 pcg 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

pcg 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 pcg tool do? +

Procedural Content Generation: graphs, nodes, connections, execution, volumes. Actions: - list_graphs: List PCG graphs. Params: directory?, recursive? - read_graph: Read graph structure. Params: assetPath - read_node_settings: Read node settings. Params: assetPath, nodeName - get_components: List PCG components in level - get_component_details: Inspect PCG component. Params: actorLabel - create_graph: Create graph. Params: name, packagePath? - add_node: Add node. Params: assetPath, nodeType, nodeName? - connect_nodes: Wire nodes. Params: assetPath, sourceNode, sourcePin, targetNode, targetPin - set_node_settings: Set node params. Params: assetPath, nodeName, settings - set_static_mesh_spawner_meshes: Populate weighted MeshEntries on a PCGStaticMeshSpawner node (#145). Params: assetPath, nodeName, entries=[{mesh, weight?}], replace? (default true) - remove_node: Remove node. Params: assetPath, nodeName - execute: Regenerate PCG. Params: actorLabel - force_regenerate: Force a stuck PCG component to regenerate (clears graph ref, re-sets, cleanup+generate). Params: actorLabel (#146) - cleanup: Cleanup a PCG component (remove spawned content). Params: actorLabel, removeComponents? (default true) (#146) - toggle_graph: Toggle a PCG component's graph assignment to force reinit (no generate). Params: actorLabel, graphPath? (#146) - add_volume: Place PCG volume. Params: graphPath, location?, extent?. 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 pcg? +

Add a rule in your Intercept YAML policy under the tools section for pcg. 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 pcg? +

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

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

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

pcg 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