AI agents call poll_hunyuan_job_status to retrieve information from Blender 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-only operation that queries the state of an asynchronous task without modifying, executing, or deleting anything. The empty description lowers confidence slightly, but the semantic meaning of 'poll_status' is unambiguously a retrieval operation. Even if it were to trigger some minor state change in logging, the primary and intended purpose is information retrieval.
From the tool's definition Tool name 'poll_hunyuan_job_status' indicates polling/querying job status. The description is empty, but the naming pattern suggests a status check operation that retrieves information without side effects.
Attacks that exploit this kind of access
poll_hunyuan_job_status. It is categorised as a Read tool in the Blender 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 Blender. 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 (silwings1986/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 →