AI agents call stream_relationship_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.
The tool appears designed to fetch and stream relationship property data from a Neo4j database. 'Stream' typically means iteratively retrieve/output data. There is no indication of write, delete, or execution capabilities. The empty description lowers confidence slightly, but the name strongly suggests a read operation with no side effects.
From the tool's definition Tool name 'stream_relationship_properties' indicates retrieval of relationship properties from a Neo4j graph. The verb 'stream' combined with 'properties' suggests querying/reading data without modification.
Attacks that exploit this kind of access
stream_relationship_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_relationship_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_relationship_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_relationship_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_relationship_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_relationship_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 →