create_finger_joint
AI agents use create_finger_joint to create or update resources in Sketchup Mcp2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sketchup Mcp2 environment.
Based on the server context (3D modeling and woodworking joinery) and sibling tools like create_dovetail and create_mortise_tenon, this tool likely creates a finger joint geometry in the 3D model — a Write operation that adds/modifies geometry reversibly. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'create_finger_joint' on a SketchUp MCP server focused on woodworking joinery operations; description is empty.
Attacks that exploit this kind of access
create_finger_joint. It is categorised as a Write tool in the Sketchup Mcp2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sketchup Mcp2 MCP server in PolicyLayer and add a rule for create_finger_joint: 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 Sketchup Mcp2. Nothing to install.
create_finger_joint 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_finger_joint 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_finger_joint. 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_finger_joint is provided by the Sketchup Mcp2 MCP server (zinin/sketchup-mcp2). 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 →