Check if PolyHaven integration is enabled in Blender. Returns a message indicating whether PolyHaven features are available.
AI agents call get_polyhaven_status to retrieve information from Tripo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about PolyHaven integration without modifying any state, creating assets, executing code, or deleting data. It is a simple informational query that fits the Read category definition of retrieving or querying data with no side effects.
From the tool's definition Tool description states it 'Check[s] if PolyHaven integration is enabled' and 'Returns a message indicating whether PolyHaven features are available.' The verb 'check' and 'returns' indicate a query operation 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 Tripo MCP Server, 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. Returns a message indicating whether PolyHaven features are available. It is categorised as a Read tool in the Tripo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tripo MCP Server 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 Tripo MCP Server. 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 Tripo MCP Server MCP server (vast-ai-research/tripo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Tripo MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Tripo MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.