This record as markdown: /tools/keeveeg-godot-mcp/set-export-filter.md
What set_export_filter does on Godot
AI agents use set_export_filter to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
filter | string | — | Export filter mode (default: all_resources) |
Parameters from the server's own tool schema.
Why set_export_filter is rated Medium
This tool modifies export filter settings for a Godot project, which is a reversible configuration change. While it affects what gets exported, it doesn't execute code, delete data, or move money. The severity is medium because misconfiguration could exclude critical resources from builds, but the effect is recoverable by adjusting the filter again.
From the tool's definition Tool name 'set_export_filter' and description 'Set which resources to include in exports' indicate modification of export configuration settings.
Attacks that exploit this kind of access
The rule that runs set_export_filter safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_export_filter, this is the rule to start with:
set_export_filter 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every set_export_filter call is checked against it from then on.
Questions about set_export_filter
Set which resources to include in exports. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
set_export_filter accepts 1 parameter: filter. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for set_export_filter: 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. Nothing to install.
set_export_filter 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 set_export_filter 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 set_export_filter. 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.
set_export_filter is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue