This record as markdown: /tools/quangdang46-uefn-verse-mcp/scatter-props.md
What scatter_props does on Uefn
AI agents invoke scatter_props to trigger actions in Uefn. 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.
Why scatter_props is rated High
Based on the tool name 'scatter_props' in the context of a UEFN editor bridge, this likely places/scatters prop actors across a scene, which constitutes triggering an external operation (modifying the live editor scene). Sibling tools like 'audio_place' suggest placement operations are common on this server.
From the tool's definition Tool name is 'scatter_props' on a UEFN (Unreal Editor for Fortnite) MCP server. Description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs scatter_props 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 scatter_props, this is the rule to start with:
scatter_props 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Uefn, apply this rule, and every scatter_props call is checked against it from then on.
Questions about scatter_props
scatter_props is a execute tool on the Uefn MCP server. 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.
Register the Uefn MCP server in PolicyLayer and add a rule for scatter_props: 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.
scatter_props 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 scatter_props 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 scatter_props. 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.
scatter_props 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