physics_set_gravity
Write the project's default gravity for 2D or 3D (ProjectSettings physics/{2d,3d}/default_gravity + default_gravity_vector). Set save=true to persist to project.godot. DESTRUCTIVE (project-wide setting) — gated by confirmation.
This record as markdown: /tools/breakpoint-mcp/physics-set-gravity.md
What physics_set_gravity does on Breakpoint
AI agents use physics_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 |
|---|---|---|---|
dim | string | — | Which gravity to set: "2d" (default) or "3d" |
save | boolean | — | Persist to project.godot (default false) |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
direction | array | — | Gravity direction vector [x, y] (2D) or [x, y, z] (3D) |
magnitude | number | — | Gravity magnitude (default 2D 980, 3D 9.8) |
Parameters from the server's own tool schema.
Why physics_set_gravity is rated Medium
This tool modifies project-wide settings (gravity) and can persist them to disk. While the description labels it DESTRUCTIVE, the change is a configuration update that could be reversed by resetting values — it doesn't irreversibly delete or overwrite data in a non-recoverable way.
From the tool's definition 'Write the project's default gravity for 2D or 3D (ProjectSettings physics/{2d,3d}/default_gravity + default_gravity_vector). Set save=true to persist to project.godot.'
Attacks that exploit this kind of access
The rule that runs physics_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 physics_set_gravity, this is the rule to start with:
physics_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 physics_set_gravity call is checked against it from then on.
Questions about physics_set_gravity
Write the project's default gravity for 2D or 3D (ProjectSettings physics/{2d,3d}/default_gravity + default_gravity_vector). Set save=true to persist to project.godot. DESTRUCTIVE (project-wide setting) — gated by confirmation. 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.
physics_set_gravity accepts 5 parameters: dim, save, confirm, direction, magnitude. 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 physics_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.
physics_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 physics_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 physics_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.
physics_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