Get the schema of the Neo4j database (node labels, relationship types, constraints, indexes)
AI agents call neo4j.get_schema to retrieve information from Neo4j MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and returns metadata about the database structure (schema information) without modifying, deleting, or executing any operations on data. It is a pure read operation with minimal blast radius if misused by an agent—at worst, an agent learns the database structure, which is informational only.
From the tool's definition Tool name 'get_schema' and description explicitly states it 'Get[s] the schema of the Neo4j database (node labels, relationship types, constraints, indexes)' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the schema of the Neo4j database (node labels, relationship types, constraints, indexes). It is categorised as a Read tool in the Neo4j MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Neo4j MCP Server MCP server in PolicyLayer and add a rule for neo4j.get_schema: 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 MCP Server. Nothing to install.
neo4j.get_schema 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 neo4j.get_schema 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 neo4j.get_schema. 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.
neo4j.get_schema is provided by the Neo4j MCP Server MCP server (vpro1032/neo4j-mcp-server). 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 →