blender_physics_force_field_add
Add a force field (wind, vortex, turbulence, etc.).
This record as markdown: /tools/wise-agent/blender-physics-force-field-add.md
What blender_physics_force_field_add does on WISE-Agent
AI agents call blender_physics_force_field_add to permanently remove resources in WISE-Agent, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why blender_physics_force_field_add is rated Critical
An AI agent that decides to call blender_physics_force_field_add doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from WISE-Agent is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs blender_physics_force_field_add 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_physics_force_field_add, this is the rule to start with:
blender_physics_force_field_add is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect WISE-Agent, apply this rule, and every blender_physics_force_field_add call is checked against it from then on.
Questions about blender_physics_force_field_add
Add a force field (wind, vortex, turbulence, etc.). It is categorised as a Destructive tool in the WISE-Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the WISE-Agent MCP server in PolicyLayer and add a rule for blender_physics_force_field_add: 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_physics_force_field_add is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the blender_physics_force_field_add 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_physics_force_field_add. 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_physics_force_field_add 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