godot_custom_command
Chama comando customizado registrado no jogo (ex: get_puzzle_state).
This record as markdown: /tools/mcp-godot-desenvolvimento/godot-custom-command.md
What godot_custom_command does on Mcp Godot Desenvolvimento
AI agents invoke godot_custom_command to trigger actions in Mcp Godot Desenvolvimento. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why godot_custom_command is rated High
This tool executes arbitrary custom commands registered within the Godot game runtime. While the example given ('get_puzzle_state') sounds like a read operation, the tool is designed to call *any* registered custom command, meaning its effects are entirely argument-dependent and could range from benign reads to destructive game-state mutations.
From the tool's definition 'Chama comando customizado registrado no jogo' — calls a custom command registered in the game, e.g. 'get_puzzle_state'
Attacks that exploit this kind of access
The rule that runs godot_custom_command safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Godot Desenvolvimento, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For godot_custom_command, this is the rule to start with:
godot_custom_command stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Godot Desenvolvimento, apply this rule, and every godot_custom_command call is checked against it from then on.
Questions about godot_custom_command
Chama comando customizado registrado no jogo (ex: get_puzzle_state). It is categorised as a Execute tool in the Mcp Godot Desenvolvimento MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Godot Desenvolvimento MCP server in PolicyLayer and add a rule for godot_custom_command: 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 Mcp Godot Desenvolvimento. Nothing to install.
godot_custom_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the godot_custom_command 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 godot_custom_command. 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.
godot_custom_command is provided by the Mcp Godot Desenvolvimento MCP server (joabcostamd/mcp-godot-desenvolvimento). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Godot Desenvolvimento, and thousands of servers like it.
Across the catalogue