AI agents use create_sketch 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.
This tool creates a new sketch, which is a reversible Write operation in parametric CAD. A sketch is a foundational design element that can be modified or deleted, but its creation commits a new model artifact. The severity is medium because misuse could create unwanted sketch geometry that clutters a design, but it is reversible and does not permanently destroy data or execute arbitrary code.
From the tool's definition Tool name is 'create_sketch' on an Autodesk Inventor MCP server described as enabling 'sketching, extrusion, hole features, and sheet metal operations.' Sibling tools include 'draw_line', 'draw_circle', 'draw_polygon', and 'create_part', which are clearly…
Attacks that exploit this kind of access
create_sketch. 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 create_sketch: 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.
create_sketch 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 create_sketch 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 create_sketch. 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.
create_sketch 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 →