AI agents use write_project_config 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 |
|---|---|---|---|
key | string | Yes | Config key to set |
value | string | Yes | Config value to set |
section | string | Yes | Section name to add or modify (e.g. "application", "rendering") |
Parameters from the server's own tool schema.
This tool creates or modifies project configuration data reversibly. While the change persists, it is not irreversibly destructive (configs can be edited or reverted) and does not delete data. The severity is high because misconfiguration of project.godot could break the Godot project, disable features, or introduce security issues, but changes are technically reversible by overwriting the config again.
From the tool's definition write_project_config: 'Write a config value to project.godot.' The tool explicitly writes/modifies configuration data to the project's central configuration file.
Attacks that exploit this kind of access
Write a config value to project.godot. 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.
write_project_config accepts 3 parameters: key, value, section. Required: key, value, section. 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 write_project_config: 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.
write_project_config 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 write_project_config 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 write_project_config. 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.
write_project_config is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
write_project_config is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →