configure_file_logging
Enable/disable engine file logging and set log_path / max_log_files in project.godot.
This record as markdown: /tools/yanhuifair-godot-mcp/configure-file-logging.md
What configure_file_logging does on Godot
AI agents use configure_file_logging 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 |
|---|---|---|---|
enabled | object | — | Turn debug/file_logging/enable_file_logging on or off. |
log_path | object | — | Log path, e.g. "user://logs/godot.log". Accepts user://, res:// or an absolute path. |
max_log_files | object | — | How many rotated logs to keep (debug/file_logging/max_log_files, default 5). |
Parameters from the server's own tool schema.
Why configure_file_logging is rated Medium
Modifies project configuration reversibly by changing logging settings and file paths in project.godot.
From the tool's definition Enable/disable engine file logging, set log_path / max_log_files in project.godot
Attacks that exploit this kind of access
The rule that runs configure_file_logging 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 configure_file_logging, this is the rule to start with:
configure_file_logging 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 configure_file_logging call is checked against it from then on.
Questions about configure_file_logging
Enable/disable engine file logging and set log_path / max_log_files in 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.
configure_file_logging accepts 3 parameters: enabled, log_path, max_log_files. 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 configure_file_logging: 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.
configure_file_logging 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 configure_file_logging 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 configure_file_logging. 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.
configure_file_logging 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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue