snap_to_ground
Snap an object's lowest point to Z=0 (the ground plane).
This record as markdown: /tools/dwgx-blender-copilot/snap-to-ground.md
What snap_to_ground does on Blender Copilot MCP Server
AI agents use snap_to_ground to create or update resources in Blender Copilot MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blender Copilot MCP Server environment.
Why snap_to_ground is rated Medium
This tool modifies object properties (spatial position) reversibly—the change can be undone or corrected by moving the object again. It does not delete data, execute arbitrary code, or trigger external operations. While it alters scene state, the modification is non-destructive and can be easily reverted, placing it in the Write category rather than Execute or Destructive.
From the tool's definition Tool description states it will 'Snap an object's lowest point to Z=0 (the ground plane)', which modifies the object's position/transformation in the Blender scene.
Attacks that exploit this kind of access
The rule that runs snap_to_ground safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Blender Copilot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snap_to_ground, this is the rule to start with:
snap_to_ground stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Blender Copilot MCP Server, apply this rule, and every snap_to_ground call is checked against it from then on.
Questions about snap_to_ground
Snap an object's lowest point to Z=0 (the ground plane). It is categorised as a Write tool in the Blender Copilot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for snap_to_ground: 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 Blender Copilot MCP Server. Nothing to install.
snap_to_ground 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 snap_to_ground 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 snap_to_ground. 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.
snap_to_ground is provided by the Blender Copilot MCP Server MCP server (dwgx/blender-copilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Blender Copilot MCP Server, and thousands of servers like it.
This server
Across the catalogue