Check if Hyper3D Rodin integration is enabled
AI agents call get_hyper3d_status to retrieve information from MCP-Blender without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves the enabled/disabled state of a Hyper3D Rodin integration feature. It is a pure read operation that queries existing state without creating, modifying, deleting, or executing any code. The blast radius of misuse is minimal—an AI agent querying this status cannot cause harm, data loss, or unintended operations.
From the tool's definition Tool name 'get_hyper3d_status' and description 'Check if Hyper3D Rodin integration is enabled' indicate a status query operation with no modification or side effects.
Attacks that exploit this kind of access
Check if Hyper3D Rodin integration is enabled. It is categorised as a Read tool in the MCP-Blender MCP Server, which means it retrieves data without modifying state.
Register the MCP-Blender MCP server in PolicyLayer and add a rule for get_hyper3d_status: 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 MCP-Blender. Nothing to install.
get_hyper3d_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_hyper3d_status 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 get_hyper3d_status. 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.
get_hyper3d_status is provided by the MCP-Blender MCP server (shdann/mcp-blend). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_hyper3d_status is one line of MCP-Blender's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →