poll_hunyuan_job_status
AI agents call poll_hunyuan_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 a job status is a read operation that retrieves state information without modifying, executing, or deleting anything. Even though the description is empty, the name and context of sibling tools strongly indicate this tool queries job completion status. The absence of description slightly lowers confidence but the semantic meaning is clear.
From the tool's definition Tool name 'poll_hunyuan_job_status' indicates status polling/checking. No description provided, but sibling tools include 'get_hunyuan3d_status' and 'get_hyper3d_status' which are clearly read operations.
Attacks that exploit this kind of access
poll_hunyuan_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_hunyuan_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_hunyuan_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_hunyuan_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_hunyuan_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_hunyuan_job_status is provided by the Blender MCP server (solonabot/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 →