get_sketchfab_model_preview
AI agents call get_sketchfab_model_preview 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.
Despite the empty description, the naming convention strongly suggests this is a retrieval operation that fetches preview information about a Sketchfab model. It aligns with the 'download_sketchfab_model' sibling tool but appears to retrieve only preview metadata/imagery rather than executing operations or modifying data. No side effects are indicated.
From the tool's definition Tool name 'get_sketchfab_model_preview' indicates retrieval of preview data/imagery from Sketchfab. The 'get_' prefix and 'preview' suffix suggest a query operation with no modification. Description is empty, reducing confidence slightly.
Attacks that exploit this kind of access
get_sketchfab_model_preview. 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_model_preview: 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_model_preview 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_model_preview 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_model_preview. 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_model_preview is provided by the Blender MCP server (opslon/blender-mcp-optimized). 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 →