poll_rodin_job_status
AI agents call poll_rodin_job_status to retrieve information from BlenderMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Polling for job status is a read-only operation that retrieves information about an asynchronous task (likely a Rodin model generation job, given the server's context around 3D model generation). This has no side effects and does not alter data, execute code, or perform destructive actions. The empty description prevents higher confidence, but the naming convention strongly indicates a status query.
From the tool's definition Tool name 'poll_rodin_job_status' indicates a status-checking operation. The word 'poll' and 'status' suggest querying state without modifying it. No description provided, which lowers confidence.
Attacks that exploit this kind of access
poll_rodin_job_status. It is categorised as a Read tool in the BlenderMCP MCP Server, which means it retrieves data without modifying state.
Register the Blender MCP server in PolicyLayer and add a rule for poll_rodin_job_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 BlenderMCP. Nothing to install.
poll_rodin_job_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 poll_rodin_job_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 poll_rodin_job_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.
poll_rodin_job_status is provided by the Blender MCP server (ujs204/claude-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 →