AI agents call stream_node_properties to retrieve information from Neo4j Gds without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description lowering confidence slightly, the tool name strongly suggests read-only access to node property data. Streaming node properties would retrieve graph metadata for analysis without modifying the database or executing external operations. This aligns with the Read category for data retrieval tools with no side effects.
From the tool's definition Tool name 'stream_node_properties' indicates retrieval/reading of node properties from a Neo4j graph. The empty description prevents direct confirmation, but the verb 'stream' and noun 'properties' suggest data retrieval rather than modification or execution.
Attacks that exploit this kind of access
stream_node_properties. It is categorised as a Read tool in the Neo4j Gds MCP Server, which means it retrieves data without modifying state.
Register the Neo4j Gds MCP server in PolicyLayer and add a rule for stream_node_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 Neo4j Gds. Nothing to install.
stream_node_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 stream_node_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 stream_node_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.
stream_node_properties is provided by the Neo4j Gds MCP server (neo4j-contrib/gds-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →