align_view_to_axis
AI agents invoke align_view_to_axis to trigger actions in BlenderMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on the tool name, this likely adjusts the viewport camera alignment in Blender to a specific axis (e.g., top, front, side view). This is an Execute-level action as it triggers a viewport operation within Blender. However, since the description is empty, confidence is low. The blast radius is low as it only affects the view orientation, not any scene data.
From the tool's definition Tool name: align_view_to_axis; description is empty/uninformative.
Attacks that exploit this kind of access
align_view_to_axis. It is categorised as a Execute tool in the BlenderMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Blender MCP server in PolicyLayer and add a rule for align_view_to_axis: 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 BlenderMCP. Nothing to install.
align_view_to_axis is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the align_view_to_axis 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 align_view_to_axis. 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.
align_view_to_axis is provided by the Blender MCP server (shirshovdim/retopoflow_blender_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 →