Low Risk

check_export_presets

Inspect Godot export presets and report pre-export issues

How to control check_export_presets ↓

AI agents call check_export_presets to retrieve information from Godot Devtool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool performs static analysis of export configuration without triggering exports, modifying presets, or executing external commands. It gathers and reports information about export settings, which is a read-only operation with no side effects or blast radius if misused by an agent.

From the tool's definition Tool name 'check_export_presets' and description 'Inspect Godot export presets and report pre-export issues' indicate a diagnostic/inspection function.

Documented attack patterns abuse exactly the kind of access check_export_presets 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 check_export_presets:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_export_presets": {}
  }
}

check_export_presets is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Godot Devtool — 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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the check_export_presets tool do? +

Inspect Godot export presets and report pre-export issues. It is categorised as a Read tool in the Godot Devtool MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_export_presets? +

Register the Godot Devtool MCP server in PolicyLayer and add a rule for check_export_presets: 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.

What risk level is check_export_presets? +

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

Can I rate-limit check_export_presets? +

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

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

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

Enforce policy on every Godot Devtool tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.