blender_quality_audit_full
Run topology + UV + performance triple audit and output a combined score.
This record as markdown: /tools/wise-agent/blender-quality-audit-full.md
What blender_quality_audit_full does on WISE-Agent
AI agents invoke blender_quality_audit_full to trigger actions in WISE-Agent. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why blender_quality_audit_full is rated High
blender_quality_audit_full triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs blender_quality_audit_full 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_quality_audit_full, this is the rule to start with:
blender_quality_audit_full stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_quality_audit_full call is checked against it from then on.
Questions about blender_quality_audit_full
Run topology + UV + performance triple audit and output a combined score. It is categorised as a Execute tool in the WISE-Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the WISE-Agent MCP server in PolicyLayer and add a rule for blender_quality_audit_full: 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_quality_audit_full is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the blender_quality_audit_full 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_quality_audit_full. 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_quality_audit_full 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.
Across the catalogue