Check if PolyHaven integration is enabled in Blender.
AI agents call get_polyhaven_status to retrieve information from Blender MCP for Antigravity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries the state of PolyHaven integration without modifying any data, executing code, or triggering external operations. It is analogous to checking a configuration flag or system status. The blast radius of misuse is minimal, as an agent cannot cause harm by repeatedly checking this status.
From the tool's definition The tool name and description indicate it 'Check[s] if PolyHaven integration is enabled' — a pure status query with no side effects.
Documented attack patterns abuse exactly the kind of access get_polyhaven_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Blender MCP for Antigravity, and nothing reaches the server without passing your rules. This is the rule we recommend for get_polyhaven_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_polyhaven_status": {}
}
}get_polyhaven_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if PolyHaven integration is enabled in Blender. It is categorised as a Read tool in the Blender MCP for Antigravity MCP Server, which means it retrieves data without modifying state.
Register the Blender MCP for Antigravity 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 Blender MCP for Antigravity. 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 for Antigravity MCP server (kc0ed/blender-mcp-for-antigravity). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Blender MCP for Antigravity, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Blender MCP for Antigravity tools catalogued and risk-classified — across an index of 43,000+ MCP servers.