This record as markdown: /tools/io-github-portel-dev-ncp/create-node.md
What create_node does on Ncp
AI agents use create_node to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why create_node is rated Medium
Creating nodes in Neo4j is a reversible write operation that adds data to the graph database. While nodes can be deleted, the primary effect here is creation/modification of data, making it a Write category tool. Severity is high because malicious node creation could corrupt the graph structure, inject malicious data, or create relationships that affect downstream queries and business logic.
From the tool's definition Tool name 'create_node' combined with description 'Create node in Neo4j graph' indicates data creation in a graph database. This is a write operation that adds new persistent data structures.
Attacks that exploit this kind of access
The rule that runs create_node safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_node, this is the rule to start with:
create_node stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every create_node call is checked against it from then on.
Questions about create_node
Create node in Neo4j graph. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp MCP server in PolicyLayer and add a rule for create_node: 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 Ncp. Nothing to install.
create_node is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_node 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 create_node. 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.
create_node is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue