AI agents use export_mesh_library to create or update resources in Godot Devtool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Devtool environment.
This tool creates or generates a new MeshLibrary resource from an existing scene. While it produces output rather than modifying existing data in-place, it is a write operation because it instantiates and persists a new resource. It is not Destructive because the original scene remains intact.
From the tool's definition Tool name 'export_mesh_library' and description 'Export a scene as a MeshLibrary resource' indicate creation/generation of a new resource file based on scene data. 'Export' implies writing data to a new file artifact.
Documented attack patterns abuse exactly the kind of access export_mesh_library gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for export_mesh_library:
{
"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.
Free to start. No card required.
Export a scene as a MeshLibrary resource. It is categorised as a Write tool in the Godot Devtool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Devtool 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 Devtool. Nothing to install.
export_mesh_library is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
export_mesh_library is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.