generate_3d_text_to_3d
AI agents invoke generate_3d_text_to_3d to trigger actions in Rodin Gen-2 MCP Server. 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.
The tool name and server context strongly suggest this tool triggers an external API call to generate 3D models from text input. This is an Execute-category action as it initiates an external operation (API call to Rodin Gen-2) whose effects depend on the text arguments provided. The description is empty, which lowers confidence.
From the tool's definition Tool name 'generate_3d_text_to_3d' and server context 'generate 3D models from text descriptions or images' via 'Rodin Gen-2 API'
Attacks that exploit this kind of access
generate_3d_text_to_3d. It is categorised as a Execute tool in the Rodin Gen-2 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Rodin Gen-2 MCP Server MCP server in PolicyLayer and add a rule for generate_3d_text_to_3d: 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 Rodin Gen-2 MCP Server. Nothing to install.
generate_3d_text_to_3d 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 generate_3d_text_to_3d 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 generate_3d_text_to_3d. 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.
generate_3d_text_to_3d is provided by the Rodin Gen-2 MCP Server MCP server (tigrondev/rodingen2mcp). 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 →