测试Blender 3.6自动检测功能，返回详细的检测结果。
AI agents call test_blender_detection_tool to retrieve information from Instant Meshes without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool tests and detects the presence/configuration of Blender 3.6, returning detection results. This is a read/query operation that checks system state without modifying anything. Confidence is slightly reduced because the description is brief and in Chinese, and 'test' tools occasionally have side effects, but the phrasing 'returns detailed detection results' strongly implies a read-only operation.
From the tool's definition 测试Blender 3.6自动检测功能，返回详细的检测结果 (Tests Blender 3.6 auto-detection functionality, returns detailed detection results)
Attacks that exploit this kind of access
测试Blender 3.6自动检测功能，返回详细的检测结果。. It is categorised as a Read tool in the Instant Meshes MCP Server, which means it retrieves data without modifying state.
Register the Instant Meshes MCP server in PolicyLayer and add a rule for test_blender_detection_tool: 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 Instant Meshes. Nothing to install.
test_blender_detection_tool 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 test_blender_detection_tool 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 test_blender_detection_tool. 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.
test_blender_detection_tool is provided by the Instant Meshes MCP server (lxy2109/instant-meshes-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 →