AI agents use set_sheet_metal_thickness 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 or modifies data reversibly—changing a thickness parameter can be undone or adjusted. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or trigger external operations with unpredictable effects.
From the tool's definition Tool modifies sheet metal style properties (thickness parameter) on an existing part. The description indicates it 'set[s]' a value, which is a modification operation. It operates on an active sheet metal style rather than deleting or destroying data.
Attacks that exploit this kind of access
Set the active sheet metal style's thickness. Use after create_part(template="sheet_metal"). 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 set_sheet_metal_thickness: 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.
set_sheet_metal_thickness 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_sheet_metal_thickness 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_sheet_metal_thickness. 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_sheet_metal_thickness 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 →