watch_state_start
Comeca a observar propriedades de nos do jogo a cada step.
This record as markdown: /tools/mcp-godot-desenvolvimento/watch-state-start.md
What watch_state_start does on Mcp Godot Desenvolvimento
AI agents invoke watch_state_start 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 watch_state_start is rated High
Starting a per-step watch on game node properties initiates an ongoing runtime process (a polling/monitoring loop tied to the game engine's step cycle). This is an external operation whose effects depend on the arguments (which nodes/properties to watch), placing it in Execute.
From the tool's definition 'Comeca a observar propriedades de nos do jogo a cada step' — triggers a recurring observation/polling loop that runs each game step, implying an active runtime operation
Attacks that exploit this kind of access
The rule that runs watch_state_start 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 watch_state_start, this is the rule to start with:
watch_state_start 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 watch_state_start call is checked against it from then on.
Questions about watch_state_start
Comeca a observar propriedades de nos do jogo a cada step. 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 watch_state_start: 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.
watch_state_start 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 watch_state_start 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 watch_state_start. 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.
watch_state_start 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