set_custom_features
Set custom feature tags for conditional compilation and export
This record as markdown: /tools/keeveeg-godot-mcp/set-custom-features.md
What set_custom_features does on Godot
AI agents use set_custom_features 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 |
|---|---|---|---|
features | array | — | List of custom feature tags (e.g. ['demo', 'mobile', 'premium']) |
Parameters from the server's own tool schema.
Why set_custom_features is rated Medium
This tool creates or modifies feature tags used by the Godot engine for conditional compilation and export behavior. While reversible (features can be changed or removed), it affects build configuration and conditional code paths, potentially impacting which code is compiled or shipped.
From the tool's definition Tool name 'set_custom_features' and description 'Set custom feature tags for conditional compilation and export' indicate modifying configuration settings.
Attacks that exploit this kind of access
The rule that runs set_custom_features 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_custom_features, this is the rule to start with:
set_custom_features 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_custom_features call is checked against it from then on.
Questions about set_custom_features
Set custom feature tags for conditional compilation and export. 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_custom_features accepts 1 parameter: features. 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_custom_features: 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_custom_features 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_custom_features 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_custom_features. 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_custom_features 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