scene_get_dependencies
List the external resource dependencies of a scene file. Read-only. Defaults to the current scene. dependencies are loadable res:// paths; dependencies_raw carries the engine's own uid://…::::res://… encoding and dependency_uids the UID alone ("" when the dependency has none) — all three index-al...
This record as markdown: /tools/breakpoint-mcp/scene-get-dependencies.md
What scene_get_dependencies does on Breakpoint
AI agents call scene_get_dependencies to retrieve information from Breakpoint 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 | — | Scene res:// path; omitted = the current edited scene |
Parameters from the server's own tool schema.
Why scene_get_dependencies is rated Low
Even though scene_get_dependencies only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs scene_get_dependencies 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 scene_get_dependencies, this is the rule to start with:
scene_get_dependencies 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 Breakpoint, apply this rule, and every scene_get_dependencies call is checked against it from then on.
Questions about scene_get_dependencies
List the external resource dependencies of a scene file. Read-only. Defaults to the current scene. dependencies are loadable res:// paths; dependencies_raw carries the engine's own uid://…::::res://… encoding and dependency_uids the UID alone ("" when the dependency has none) — all three index-aligned. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
scene_get_dependencies accepts 1 parameter: 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 scene_get_dependencies: 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.
scene_get_dependencies 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 scene_get_dependencies 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 scene_get_dependencies. 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.
scene_get_dependencies 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