blender_describe_object
Deep inspection of a single object: topology stats (verts/edges/faces/ngons),
This record as markdown: /tools/wise-agent/blender-describe-object.md
What blender_describe_object does on WISE-Agent
AI agents call blender_describe_object to retrieve information from WISE-Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why blender_describe_object is rated Low
Even though blender_describe_object only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs blender_describe_object safely
PolicyLayer is an MCP gateway: it sits between your AI agents and WISE-Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blender_describe_object, this is the rule to start with:
blender_describe_object 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 WISE-Agent, apply this rule, and every blender_describe_object call is checked against it from then on.
Questions about blender_describe_object
Deep inspection of a single object: topology stats (verts/edges/faces/ngons),. It is categorised as a Read tool in the WISE-Agent MCP Server, which means it retrieves data without modifying state.
Register the WISE-Agent MCP server in PolicyLayer and add a rule for blender_describe_object: 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 WISE-Agent. Nothing to install.
blender_describe_object 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_describe_object 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_describe_object. 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_describe_object is provided by the WISE-Agent MCP server (qwzx4893-stack/WISE-Agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on WISE-Agent, and thousands of servers like it.
This server
Across the catalogue