node_get_property
Read a single property from a node. Rich types come back __type__-tagged.
This record as markdown: /tools/breakpoint-mcp/node-get-property.md
What node_get_property does on Breakpoint
AI agents call node_get_property 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 |
property | string | Yes | Property name |
Parameters from the server's own tool schema.
Why node_get_property is rated Low
This tool retrieves node properties without modifying, executing, or destroying anything. It is a straightforward read operation with minimal blast radius if misused by an AI agent—worst case would be accessing properties it shouldn't, which is a confidentiality concern but not an integrity or availability risk.
From the tool's definition Tool description explicitly states 'Read a single property from a node' with no side effects mentioned. The verb 'read' and context of retrieving property values with return type tagging confirms data retrieval only.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs node_get_property 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_get_property, this is the rule to start with:
node_get_property 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_get_property call is checked against it from then on.
Questions about node_get_property
Read a single property from a node. Rich types come back __type__-tagged. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
node_get_property accepts 2 parameters: path, property. Required: path, property. 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_get_property: 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_get_property 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_get_property 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_get_property. 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_get_property 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