This record as markdown: /tools/hybridlabor-api-aos/set-user-text.md
What set_user_text does on Aos
AI agents use set_user_text to create or update resources in Aos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aos environment.
Why set_user_text is rated Medium
The tool modifies object properties (user text metadata) in Rhino, which is reversible and does not delete data or execute arbitrary code. It fits the Write category. Severity is medium because misuse could corrupt object metadata, affecting design workflows, but the impact is localized to metadata and can be undone.
From the tool's definition Tool name 'set_user_text' and description 'Set a user-text key-value pair on an object' indicates creation or modification of metadata on Rhino objects. This is a reversible Write operation—the key-value pair can be updated or removed.
Attacks that exploit this kind of access
The rule that runs set_user_text safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_user_text, this is the rule to start with:
set_user_text 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 Aos, apply this rule, and every set_user_text call is checked against it from then on.
Questions about set_user_text
Set a user-text key-value pair on an object. It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aos MCP server in PolicyLayer and add a rule for set_user_text: 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 Aos. Nothing to install.
set_user_text 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_user_text 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_user_text. 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_user_text is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue