This record as markdown: /tools/chanceflow-godot-mcp/timer-add.md
What timer_add does on Godot
AI agents use timer_add 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.
Why timer_add is rated Medium
The 'add' verb strongly suggests a Write operation that creates or modifies Godot scene/object state (likely adding a Timer node to a scene). This is reversible (timers can be removed), so it does not qualify as Destructive. Severity is medium because misuse could cause unwanted timer behavior affecting game logic, but the blast radius is limited to a single game scene's timing behavior.
From the tool's definition Tool name 'timer_add' suggests creating or adding a timer object/resource in Godot. The verb 'add' indicates a creation/modification action. Description is empty, limiting evidence.
Attacks that exploit this kind of access
The rule that runs timer_add 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 timer_add, this is the rule to start with:
timer_add 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 timer_add call is checked against it from then on.
Questions about timer_add
timer_add is a write tool on the Godot MCP server. 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.
Register the Godot MCP server in PolicyLayer and add a rule for timer_add: 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.
timer_add 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 timer_add 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 timer_add. 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.
timer_add is provided by the Godot MCP server (chanceflow/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