node_list_properties
List a node's inspector-visible properties (name, Variant type, class_name, usage flags). Read-only. Use node_get_property to read a value.
This record as markdown: /tools/breakpoint-mcp/node-list-properties.md
What node_list_properties does on Breakpoint
AI agents call node_list_properties 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 | Yes | Node path relative to the scene root |
Parameters from the server's own tool schema.
Why node_list_properties is rated Low
This tool retrieves metadata about nodes (name, type, class, flags) without side effects. It is purely informational and safe for an AI agent to use. The explicit 'Read-only' designation and lack of any write/execute/delete capability place it firmly in the Read category with low severity.
From the tool's definition Tool description explicitly states 'Read-only' and 'List a node's inspector-visible properties'. The name 'node_list_properties' indicates data retrieval with no modification. Description confirms it does not write or execute, only 'list' properties.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs node_list_properties 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 node_list_properties, this is the rule to start with:
node_list_properties 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 node_list_properties call is checked against it from then on.
Questions about node_list_properties
List a node's inspector-visible properties (name, Variant type, class_name, usage flags). Read-only. Use node_get_property to read a value. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
node_list_properties accepts 1 parameter: path. 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 node_list_properties: 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.
node_list_properties 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 node_list_properties 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 node_list_properties. 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.
node_list_properties 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