Create a new node in the NodeSpace knowledge graph.
AI agents use nodespace_create_node to create or update resources in Nodespace — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodespace environment.
This tool creates new entries in a knowledge graph, which is a reversible modification of data. It does not execute code, delete data irreversibly, or move money. An AI agent misusing this could pollute the knowledge base with incorrect or malicious entries, requiring manual cleanup. Medium severity reflects the reversible nature and localized impact within a project's knowledge base.
From the tool's definition Tool name 'nodespace_create_node' and description 'Create a new node in the NodeSpace knowledge graph' explicitly indicate data creation.
Documented attack patterns abuse exactly the kind of access nodespace_create_node gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nodespace, and nothing reaches the server without passing your rules. This is the rule we recommend for nodespace_create_node:
{
"version": "1",
"default": "deny",
"tools": {
"nodespace_create_node": {
"limits": [
{
"counter": "nodespace_create_node_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}nodespace_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.
Free to start. No card required.
Create a new node in the NodeSpace knowledge graph. It is categorised as a Write tool in the Nodespace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nodespace MCP server in PolicyLayer and add a rule for nodespace_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 Nodespace. Nothing to install.
nodespace_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 nodespace_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 nodespace_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.
nodespace_create_node is provided by the Nodespace MCP server (nodespaceai/nodespace-core). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nodespace, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Nodespace tools catalogued and risk-classified — across an index of 43,000+ MCP servers.