join_curves
Join multiple open curves into one or more polycurves.
This record as markdown: /tools/hybridlabor-api-aos/join-curves.md
What join_curves does on Aos
AI agents use join_curves 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 join_curves is rated Medium
This tool modifies geometric data by joining curves into polycurves, which is a reversible write operation. It creates new geometric entities but does not execute arbitrary code, delete data irreversibly, or trigger financial transactions.
From the tool's definition Tool name 'join_curves' and description 'Join multiple open curves into one or more polycurves' indicates creation/modification of geometry objects through combining existing curves into new polycurve structures.
Attacks that exploit this kind of access
The rule that runs join_curves 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 join_curves, this is the rule to start with:
join_curves 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 join_curves call is checked against it from then on.
Questions about join_curves
Join multiple open curves into one or more polycurves. 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 join_curves: 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.
join_curves 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 join_curves 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 join_curves. 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.
join_curves 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