blender_vr_preview_start

Start VR preview

SERVERWISE-Agent SOURCEqwzx4893-stack/WISE-Agent

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/wise-agent/blender-vr-preview-start.md

WHAT IT DOES

What blender_vr_preview_start does on WISE-Agent

AI agents invoke blender_vr_preview_start 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.

RISK

Why blender_vr_preview_start is rated High

blender_vr_preview_start 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

RECOMMENDED RULE

The rule that runs blender_vr_preview_start 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_vr_preview_start, this is the rule to start with:

blender_vr_preview_start Rate-limited

blender_vr_preview_start 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "blender_vr_preview_start": {
      "limits": [
        {
          "counter": "blender_vr_preview_start_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect WISE-Agent, apply this rule, and every blender_vr_preview_start call is checked against it from then on.

FAQ

Questions about blender_vr_preview_start

What does the blender_vr_preview_start tool do? +

Start VR preview. 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.

How do I enforce a policy on blender_vr_preview_start? +

Register the WISE-Agent MCP server in PolicyLayer and add a rule for blender_vr_preview_start: 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.

What risk level is blender_vr_preview_start? +

blender_vr_preview_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit blender_vr_preview_start? +

Yes. Add a rate_limit block to the blender_vr_preview_start 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.

How do I block blender_vr_preview_start completely? +

Set action: deny in the PolicyLayer policy for blender_vr_preview_start. 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.

What MCP server provides blender_vr_preview_start? +

blender_vr_preview_start 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.

KEEP EXPLORING

More on WISE-Agent, and thousands of servers like it.

This server

All 378 WISE-Agent tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →