Add a through hole with diameter
AI agents use add_through_hole to create or update resources in Hardware MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hardware MCP Server environment.
This tool modifies a CAD design by adding a hole feature—a standard parametric modeling operation. The change is reversible (the CAD model can be reloaded or the hole removed in a subsequent operation), making it Write rather than Destructive.
From the tool's definition Tool name 'add_through_hole' and description 'Add a through hole with diameter' indicate modification of CAD geometry.
Attacks that exploit this kind of access
Add a through hole with diameter. It is categorised as a Write tool in the Hardware MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hardware MCP Server MCP server in PolicyLayer and add a rule for add_through_hole: 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 Hardware MCP Server. Nothing to install.
add_through_hole 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 add_through_hole 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 add_through_hole. 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.
add_through_hole is provided by the Hardware MCP Server MCP server (thefloatingstring/mcp-for-hardware). 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 →