area_set_gravity
Set the local gravity override of an Area2D/3D in the edited scene (undoable): space_override mode, gravity magnitude, direction, and whether gravity points toward a center (point). In-scene and undoable — not gated.
This record as markdown: /tools/breakpoint-mcp/area-set-gravity.md
What area_set_gravity does on Breakpoint
AI agents use area_set_gravity to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Area2D/3D node path relative to the scene root |
point | boolean | — | If true, gravity pulls toward the area's gravity point instead of a direction |
gravity | number | — | Gravity magnitude (units/s^2) |
direction | array | — | Gravity direction [x, y] (2D) or [x, y, z] (3D) |
space_override | string | — | How this area's gravity combines with the global/other areas |
Parameters from the server's own tool schema.
Why area_set_gravity is rated Medium
This tool modifies a property of a scene node (gravity settings on an Area2D/3D). It is explicitly described as undoable, meaning the action is reversible. This fits the Write category — it creates or modifies data reversibly. The severity is medium because misuse could alter game physics behavior in the edited scene, but it is undoable and scoped to the editor environment.
From the tool's definition Set the local gravity override of an Area2D/3D in the edited scene (undoable)
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs area_set_gravity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For area_set_gravity, this is the rule to start with:
area_set_gravity 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 Breakpoint, apply this rule, and every area_set_gravity call is checked against it from then on.
Questions about area_set_gravity
Set the local gravity override of an Area2D/3D in the edited scene (undoable): space_override mode, gravity magnitude, direction, and whether gravity points toward a center (point). In-scene and undoable — not gated. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
area_set_gravity accepts 5 parameters: path, point, gravity, direction, space_override. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for area_set_gravity: 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 Breakpoint. Nothing to install.
area_set_gravity 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_gravity 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_gravity. 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_gravity is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue