navregion_create
Add a NavigationRegion3D under a parent (undoable). By default seeds a fresh empty NavigationMesh (set with_navmesh=false to skip). Returns the new node's path and whether a navmesh was attached.
This record as markdown: /tools/breakpoint-mcp/navregion-create.md
What navregion_create does on Breakpoint
AI agents use navregion_create 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 |
|---|---|---|---|
name | string | — | Node name (default NavigationRegion3D) |
parent_path | string | Yes | Parent node path relative to the scene root; "." for the root |
with_navmesh | boolean | — | Seed a fresh empty NavigationMesh resource (default true) |
Parameters from the server's own tool schema.
Why navregion_create is rated Medium
This tool creates and modifies scene structure by adding a new NavigationRegion3D node and optionally seeding a NavigationMesh. This is a reversible Write operation (undoable), not Execute or Destructive. Severity is medium because uncontrolled node creation could pollute scene structure, increase memory usage, or interfere with navigation systems, but damage can be undone.
From the tool's definition Tool description states 'Add a NavigationRegion3D under a parent (undoable)' — creates a new navigation node with associated mesh data. The '(undoable)' qualifier indicates reversibility through undo functionality.
Attacks that exploit this kind of access
The rule that runs navregion_create 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 navregion_create, this is the rule to start with:
navregion_create 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 navregion_create call is checked against it from then on.
Questions about navregion_create
Add a NavigationRegion3D under a parent (undoable). By default seeds a fresh empty NavigationMesh (set with_navmesh=false to skip). Returns the new node's path and whether a navmesh was attached. 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.
navregion_create accepts 3 parameters: name, parent_path, with_navmesh. Required: parent_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 navregion_create: 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.
navregion_create 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 navregion_create 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 navregion_create. 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.
navregion_create 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