AI agents invoke remote_call to trigger actions in Unreal. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The name 'remote_call' strongly implies executing remote procedure calls or API operations on an external system (Unreal Engine). Given the server context involves manipulating 3D objects and controlling an editor, this tool likely triggers operations in Unreal Engine.
From the tool's definition Tool name is 'remote_call' on a server that interacts with Unreal Engine 5.3 via Remote Control API
Documented attack patterns abuse exactly the kind of access remote_call gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unreal, and nothing reaches the server without passing your rules. This is the rule we recommend for remote_call:
{
"version": "1",
"default": "deny",
"tools": {
"remote_call": {
"limits": [
{
"counter": "remote_call_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}remote_call stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
remote_call. It is categorised as a Execute tool in the Unreal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unreal MCP server in PolicyLayer and add a rule for remote_call: 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. Nothing to install.
remote_call is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the remote_call 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 remote_call. 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.
remote_call is provided by the Unreal MCP server (runeape-sats/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Unreal tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Unreal tools catalogued and risk-classified — across an index of 42,500+ MCP servers.