set_tags
Add, remove, and/or clear gameplay tags on one object (id) or many (ids). Tags drive collision groups, queries, and triggers.
This record as markdown: /tools/sbox/set-tags.md
What set_tags does on Sbox
AI agents use set_tags 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_tags is rated Medium
This tool modifies data (tags) on game objects, which qualifies it as Write rather than Execute or Destructive. While tag changes could indirectly affect gameplay behavior through collision/trigger systems, the operation itself is reversible and non-destructive. Severity is medium because misuse could disrupt game mechanics or object interactions, but effects are containable and reversible.
From the tool's definition Tool description states it can 'Add, remove, and/or clear gameplay tags on one object (id) or many (ids).' These are reversible modifications to game object metadata. Tags affect collision groups, queries, and triggers — core gameplay mechanics.
Attacks that exploit this kind of access
The rule that runs set_tags 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_tags, this is the rule to start with:
set_tags 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_tags call is checked against it from then on.
Questions about set_tags
Add, remove, and/or clear gameplay tags on one object (id) or many (ids). Tags drive collision groups, queries, and triggers. 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_tags: 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_tags 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_tags 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_tags. 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_tags 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