enable_debug_collisions
Ativa ou desativa a visualizacao de collision shapes no projeto.
This record as markdown: /tools/mcp-godot-desenvolvimento/enable-debug-collisions.md
What enable_debug_collisions does on Mcp Godot Desenvolvimento
AI agents invoke enable_debug_collisions 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 enable_debug_collisions is rated High
This tool toggles a debug visualization setting within a Godot project, which is an operation that triggers a change in the runtime/editor state. It doesn't merely read data, nor does it destructively delete anything. It executes a configuration change affecting the project's debug rendering behavior, making Execute the most appropriate category.
From the tool's definition Ativa ou desativa a visualizacao de collision shapes no projeto
Attacks that exploit this kind of access
The rule that runs enable_debug_collisions 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 enable_debug_collisions, this is the rule to start with:
enable_debug_collisions 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 enable_debug_collisions call is checked against it from then on.
Questions about enable_debug_collisions
Ativa ou desativa a visualizacao de collision shapes no projeto. 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 enable_debug_collisions: 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.
enable_debug_collisions 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 enable_debug_collisions 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 enable_debug_collisions. 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.
enable_debug_collisions 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