This record as markdown: /tools/hybridlabor-api-aos/offset-surface.md
What offset_surface does on Aos
AI agents use offset_surface 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 offset_surface is rated Medium
Based on the tool name, 'offset_surface' most likely creates a new surface offset from an existing one — a geometry creation/modification operation. This is consistent with standard 3D modeling terminology and the server context (Rhino 8 geometry creation). It is classified as Write since it creates or modifies geometry reversibly. Confidence is lowered due to the empty description.
From the tool's definition Tool name 'offset_surface' on a Rhino 3D MCP server; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs offset_surface 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 offset_surface, this is the rule to start with:
offset_surface 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 offset_surface call is checked against it from then on.
Questions about offset_surface
offset_surface is a write tool on the Aos MCP server. 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 offset_surface: 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.
offset_surface 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 offset_surface 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 offset_surface. 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.
offset_surface 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