Check if PolyHaven integration is enabled in Blender.
AI agents call get_polyhaven_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.
This tool only retrieves the current status of an integration—it queries state without modifying, deleting, executing, or moving anything. It is a read-only diagnostic operation, the least risky category.
From the tool's definition Tool name and description indicate a status check operation: 'Check if PolyHaven integration is enabled in Blender.' The word 'check' and 'status' are diagnostic/query operations with no side effects.
Attacks that exploit this kind of access
Check if PolyHaven integration is enabled in Blender. 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 get_polyhaven_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.
get_polyhaven_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_polyhaven_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_polyhaven_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_polyhaven_status is provided by the Blender MCP server (johncarlo177/python.blendermcp). 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 →