device_set_property
A write tool on the Uefn MCP server.
This record as markdown: /tools/quangdang46-uefn-verse-mcp/device-set-property.md
What device_set_property does on Uefn
AI agents use device_set_property to create or update resources in Uefn, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Uefn environment.
Why device_set_property is rated Medium
The tool appears to modify device properties reversibly without deleting data or executing arbitrary code. Classified as Write rather than Execute because property-setting operations typically change configuration state rather than trigger external processes or shell commands.
From the tool's definition Tool name 'device_set_property' indicates modification of device properties. No description provided, but the naming pattern and context within a UEFN editor (Unreal Editor for Fortnite) bridge suggests this sets properties on in-editor objects.
Attacks that exploit this kind of access
The rule that runs device_set_property safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Uefn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For device_set_property, this is the rule to start with:
device_set_property 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 Uefn, apply this rule, and every device_set_property call is checked against it from then on.
Questions about device_set_property
device_set_property is a write tool on the Uefn MCP server. It is categorised as a Write tool in the Uefn MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Uefn MCP server in PolicyLayer and add a rule for device_set_property: 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.
device_set_property 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 device_set_property 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 device_set_property. 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.
device_set_property 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.
More on Uefn, and thousands of servers like it.
This server
Across the catalogue