blender.export

Queue safe headless GLB export of the authoritative imported Blender scene.

SERVERVisionmcp SOURCEjoshuahickscorp/visionmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/visionmcp/blender.export.md

WHAT IT DOES

What blender.export does on Visionmcp

AI agents call blender.export to retrieve information from Visionmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why blender.export is rated Low

Even though blender.export 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

RECOMMENDED RULE

The rule that runs blender.export safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Visionmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blender.export, this is the rule to start with:

blender.export Allowed

blender.export is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "blender.export": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Visionmcp, apply this rule, and every blender.export call is checked against it from then on.

FAQ

Questions about blender.export

What does the blender.export tool do? +

Queue safe headless GLB export of the authoritative imported Blender scene. It is categorised as a Read tool in the Visionmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on blender.export? +

Register the Vision MCP server in PolicyLayer and add a rule for blender.export: 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 Visionmcp. Nothing to install.

What risk level is blender.export? +

blender.export is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit blender.export? +

Yes. Add a rate_limit block to the blender.export 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.export completely? +

Set action: deny in the PolicyLayer policy for blender.export. 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.export? +

blender.export is provided by the Vision MCP server (joshuahickscorp/visionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vision, and thousands of servers like it.

This server

All 376 Vision tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →