device_call_method

THE RISK

High Risk

Why device_call_method needs a policy

The name 'device_call_method' strongly suggests executing a method/function call on a device object in the live UEFN editor. Method calls can trigger arbitrary operations in the editor, including state changes, side effects, or destructive actions.

From the tool's definition Tool name 'device_call_method' implies invoking a method on a device within the UEFN editor environment.

Documented attack patterns abuse exactly the kind of access device_call_method gives an agent:

POLICY

How to control device_call_method

PolicyLayer is an MCP gateway — it sits between your AI agents and Uefn, and nothing reaches the server without passing your rules. This is the rule we recommend for device_call_method:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "device_call_method": {
      "limits": [
        {
          "counter": "device_call_method_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

device_call_method 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.

Create a free account and register Uefn — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Uefn tools

Destructive delete_actors Delete actors by their labels. Destructive delete_asset Delete an asset. Destructive tag_remove tag_remove Destructive shutdown Stop the MCP listener. Destructive snapshot_restore Restore the level to a previously saved snapshot state. Destructive undo Undo the last editor action via the transaction system. Execute batch_exec Execute multiple bridge commands in a single editor tick — faster than sending one-by-one. Execute blueprint_compile Compile a Blueprint asset and return compilation status.

All 143 Uefn tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Uefn → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about device_call_method

What does the device_call_method tool do? +

device_call_method. It is categorised as a Execute tool in the Uefn MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on device_call_method? +

Register the Uefn MCP server in PolicyLayer and add a rule for device_call_method: 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.

What risk level is device_call_method? +

device_call_method is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit device_call_method? +

Yes. Add a rate_limit block to the device_call_method 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.

How do I block device_call_method completely? +

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

device_call_method 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.

Enforce policy on every Uefn tool call.

Start from Uefn, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →