Medium Risk

export_mesh_library

Export a scene as a MeshLibrary resource

How to control export_mesh_library ↓

What export_mesh_library does on Godot MCP

AI agents use export_mesh_library to create or update resources in Godot MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP environment.

Medium Risk

Why export_mesh_library needs a policy

Exporting a scene as a MeshLibrary creates a new asset file in the project, which is a reversible write operation. While it generates/writes data to disk, it does not execute arbitrary code, delete existing assets, or involve financial transactions.

From the tool's definition Tool is named 'export_mesh_library' and described as 'Export a scene as a MeshLibrary resource', indicating it creates/generates a new resource file in the Godot project

Documented attack patterns abuse exactly the kind of access export_mesh_library gives an agent:

How to control export_mesh_library

PolicyLayer is an MCP gateway — it sits between your AI agents and Godot MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for export_mesh_library:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_mesh_library": {
      "limits": [
        {
          "counter": "export_mesh_library_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

export_mesh_library stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Godot MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about export_mesh_library

What does the export_mesh_library tool do? +

Export a scene as a MeshLibrary resource. It is categorised as a Write tool in the Godot MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on export_mesh_library? +

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

What risk level is export_mesh_library? +

export_mesh_library is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit export_mesh_library? +

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

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

export_mesh_library is provided by the Godot MCP server (leesinliang/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Godot MCP tool call.

Start from Godot MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

18 Godot MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.