Check if PolyHaven integration is enabled
AI agents call get_polyhaven_status to retrieve information from MCP-Blender without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple status check query against PolyHaven integration configuration. It retrieves information (enabled/disabled state) with no side effects, no data modifications, no code execution, and no destructive operations. The blast radius of misuse is minimal—an AI agent cannot cause harm by querying whether a feature is enabled. This is a straightforward Read category tool.
From the tool's definition Tool name 'get_polyhaven_status' and description 'Check if PolyHaven integration is enabled' indicate a read-only query operation that retrieves status information without modifying any state.
Attacks that exploit this kind of access
Check if PolyHaven integration is enabled. It is categorised as a Read tool in the MCP-Blender MCP Server, which means it retrieves data without modifying state.
Register the MCP-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 MCP-Blender. 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 MCP-Blender MCP server (shdann/mcp-blend). 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 →