set_ownership
Transfer network ownership of a GameObject to a different connection, or take/drop ownership
This record as markdown: /tools/sbox/set-ownership.md
What set_ownership does on Sbox
AI agents use set_ownership to create or update resources in Sbox, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sbox environment.
Why set_ownership is rated Medium
This tool modifies the ownership state of a networked GameObject, which is a reversible write operation (ownership can be transferred again). It does not delete data or execute arbitrary code, but misuse could disrupt multiplayer game state by reassigning control of objects to unintended connections.
From the tool's definition Transfer network ownership of a GameObject to a different connection, or take/drop ownership
Attacks that exploit this kind of access
The rule that runs set_ownership safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sbox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_ownership, this is the rule to start with:
set_ownership 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 Sbox, apply this rule, and every set_ownership call is checked against it from then on.
Questions about set_ownership
Transfer network ownership of a GameObject to a different connection, or take/drop ownership. It is categorised as a Write tool in the Sbox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sbox MCP server in PolicyLayer and add a rule for set_ownership: 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 Sbox. Nothing to install.
set_ownership 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 set_ownership 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 set_ownership. 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.
set_ownership is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sbox, and thousands of servers like it.
This server
Across the catalogue