add_event_node
Add an event node (ReceiveBeginPlay, ReceiveTick, ReceiveDestroyed, etc.).
This record as markdown: /tools/aadeshrao123-unreal-mcp/add-event-node.md
What add_event_node does on Unreal-MCP
AI agents use add_event_node to create or update resources in Unreal-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unreal-MCP environment.
Why add_event_node is rated Medium
The tool creates new event nodes in Unreal Engine blueprints, modifying the blueprint's logic flow. This is a Write operation because it creates new blueprint elements reversibly—nodes can be deleted or modified. It is not Destructive (nodes aren't irreversibly deleted), Execute (doesn't run external code or shell commands directly), or Financial.
From the tool's definition Tool adds an event node to Unreal Engine blueprints. The description explicitly states it creates nodes (ReceiveBeginPlay, ReceiveTick, ReceiveDestroyed, etc.), which are blueprint elements that define event handlers.
Attacks that exploit this kind of access
The rule that runs add_event_node safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_event_node, this is the rule to start with:
add_event_node 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 Unreal-MCP, apply this rule, and every add_event_node call is checked against it from then on.
Questions about add_event_node
Add an event node (ReceiveBeginPlay, ReceiveTick, ReceiveDestroyed, etc.). It is categorised as a Write tool in the Unreal-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unreal MCP server in PolicyLayer and add a rule for add_event_node: 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 Unreal-MCP. Nothing to install.
add_event_node 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 add_event_node 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 add_event_node. 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.
add_event_node is provided by the Unreal MCP server (aadeshrao123/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unreal, and thousands of servers like it.
This server
Across the catalogue