area_set_monitoring
Set monitoring and/or monitorable on an Area2D/3D in the edited scene (undoable). monitoring = the area detects overlapping bodies/areas; monitorable = other areas can detect it. In-scene and undoable — not gated.
This record as markdown: /tools/godot-breakpoint-mcp/area-set-monitoring.md
What area_set_monitoring does on Godot Breakpoint
AI agents use area_set_monitoring to create or update resources in Godot Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Breakpoint environment.
Why area_set_monitoring is rated Medium
This tool modifies the state of Area2D/3D nodes in the Godot editor scene by changing physics detection properties. While these are configuration changes (not destructive deletes), they constitute data modification that affects scene behavior. The explicit mention of 'undoable' confirms reversibility, placing this in Write rather than Destructive.
From the tool's definition Tool description states it 'Set[s] monitoring and/or monitorable on an Area2D/3D' and explicitly notes the action is '(undoable)', confirming the changes are reversible and modify scene state rather than being destructive.
Attacks that exploit this kind of access
The rule that runs area_set_monitoring safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For area_set_monitoring, this is the rule to start with:
area_set_monitoring 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 Breakpoint, apply this rule, and every area_set_monitoring call is checked against it from then on.
Questions about area_set_monitoring
Set monitoring and/or monitorable on an Area2D/3D in the edited scene (undoable). monitoring = the area detects overlapping bodies/areas; monitorable = other areas can detect it. In-scene and undoable — not gated. It is categorised as a Write tool in the Godot Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for area_set_monitoring: 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 Breakpoint. Nothing to install.
area_set_monitoring 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 area_set_monitoring 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 area_set_monitoring. 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.
area_set_monitoring is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot Breakpoint, and thousands of servers like it.
This server
Across the catalogue