set_scripting_backend
Set the scripting backend for the project
This record as markdown: /tools/keeveeg-godot-mcp/set-scripting-backend.md
What set_scripting_backend does on Godot
AI agents use set_scripting_backend 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 |
|---|---|---|---|
backend | string | — | Scripting language backend: gdscript or csharp (default: gdscript) |
Parameters from the server's own tool schema.
Why set_scripting_backend is rated Medium
This tool modifies project settings (the scripting backend choice), which is a reversible configuration change. It does not execute arbitrary code, delete data, or move money. However, the severity is elevated to 'high' because changing the scripting backend could have significant downstream effects on project functionality—it affects how all scripts in the project are interpreted or compiled.
From the tool's definition Tool name 'set_scripting_backend' and description 'Set the scripting backend for the project' indicate modification of project configuration settings.
Attacks that exploit this kind of access
The rule that runs set_scripting_backend 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_scripting_backend, this is the rule to start with:
set_scripting_backend 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_scripting_backend call is checked against it from then on.
Questions about set_scripting_backend
Set the scripting backend for the project. 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_scripting_backend accepts 1 parameter: backend. 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_scripting_backend: 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_scripting_backend 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_scripting_backend 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_scripting_backend. 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_scripting_backend 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