Check if Sketchfab integration is enabled in Blender.
AI agents call get_sketchfab_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 performs a simple status check that returns information about whether a feature is enabled. It has no side effects, does not execute code or commands, does not modify data, and does not delete or move resources. It is purely informational, fitting the Read category with low severity since an AI agent misusing it would only retrieve harmless configuration state information.
From the tool's definition Tool name and description indicate it 'checks' or queries the status of Sketchfab integration—a read-only operation that retrieves state information without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Check if Sketchfab 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_sketchfab_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_sketchfab_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_sketchfab_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_sketchfab_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_sketchfab_status is provided by the Blender MCP server (solonabot/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 →