AI agents use circular_pattern to create or update resources in Inventor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Inventor environment.
In Autodesk Inventor, 'circular_pattern' creates a circular pattern of features or bodies — it creates/modifies a 3D model by duplicating features around an axis. This is a Write operation (creates new geometry/features reversibly, as parametric models allow deletion). Confidence is low because the description is empty, but the tool name and server context strongly suggest a feature-creation operation.
From the tool's definition Tool name 'circular_pattern' in context of a parametric 3D modeling MCP server for Autodesk Inventor
Attacks that exploit this kind of access
circular_pattern. It is categorised as a Write tool in the Inventor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Inventor MCP server in PolicyLayer and add a rule for circular_pattern: 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 Inventor. Nothing to install.
circular_pattern 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 circular_pattern 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 circular_pattern. 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.
circular_pattern is provided by the Inventor MCP server (neonglay/inventor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →