monitor_properties
🔴 Game must be running. Monitor specific properties on a game node for changes over time
This record as markdown: /tools/keeveeg-godot-mcp/monitor-properties.md
What monitor_properties does on Godot
AI agents call monitor_properties to retrieve information from Godot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Node path to monitor |
duration | number | — | Monitoring duration in seconds |
properties | array | Yes | Property names to monitor |
Parameters from the server's own tool schema.
Why monitor_properties is rated Low
The tool observes and reports on property changes in a running Godot game but does not create, modify, delete, or execute arbitrary operations. Monitoring is fundamentally a read operation with no side effects. The requirement that 'Game must be running' further confirms this is passive inspection rather than an action that changes state.
From the tool's definition Tool name 'monitor_properties' with description 'Monitor specific properties on a game node for changes over time' indicates passive observation/querying of property values without modification.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs monitor_properties 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 monitor_properties, this is the rule to start with:
monitor_properties is read-only, so it stays allowed. 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 monitor_properties call is checked against it from then on.
Questions about monitor_properties
🔴 Game must be running. Monitor specific properties on a game node for changes over time. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
monitor_properties accepts 3 parameters: path, duration, properties. Required: path, properties. 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 monitor_properties: 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.
monitor_properties is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the monitor_properties 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 monitor_properties. 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.
monitor_properties 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