blender_search_tools
A read tool on the Blender MCP server.
This record as markdown: /tools/sandraschi-blender-mcp/blender-search-tools.md
What blender_search_tools does on Blender
AI agents call blender_search_tools to retrieve information from Blender without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why blender_search_tools is rated Low
Despite the empty description reducing confidence slightly, the semantic meaning of 'search' in the context of a Blender control server most naturally maps to querying or listing available tools/resources. Search operations are typically non-destructive and return data without side effects. The lack of explicit language indicating modification, execution, or deletion supports the Read category.
From the tool's definition Tool name 'blender_search_tools' suggests a search/discovery function. No description provided, but 'search' verbs typically indicate read-only query operations that retrieve information without modifying state.
Attacks that exploit this kind of access
The rule that runs blender_search_tools safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Blender, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blender_search_tools, this is the rule to start with:
blender_search_tools is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Blender, apply this rule, and every blender_search_tools call is checked against it from then on.
Questions about blender_search_tools
blender_search_tools is a read tool on the Blender MCP server. It is categorised as a Read tool in the Blender MCP Server, which means it retrieves data without modifying state.
Register the Blender MCP server in PolicyLayer and add a rule for blender_search_tools: 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. Nothing to install.
blender_search_tools 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 blender_search_tools 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 blender_search_tools. 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.
blender_search_tools is provided by the Blender MCP server (sandraschi/blender-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Blender, and thousands of servers like it.
This server
Across the catalogue