List the direct children of a NodeSpace node.
AI agents call nodespace_get_children to retrieve information from Nodespace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves hierarchical information from a local knowledge base without creating, modifying, or deleting data. It is a simple read operation that queries existing node structure. The low severity reflects minimal blast radius—an AI agent misusing this tool can only over-query or expose information already stored locally, without external impact.
From the tool's definition Tool name 'nodespace_get_children' and description 'List the direct children of a NodeSpace node' indicate a retrieval/query operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access nodespace_get_children 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_get_children:
{
"version": "1",
"default": "deny",
"tools": {
"nodespace_get_children": {}
}
}nodespace_get_children is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List the direct children of a NodeSpace node. It is categorised as a Read tool in the Nodespace MCP Server, which means it retrieves data without modifying state.
Register the Nodespace MCP server in PolicyLayer and add a rule for nodespace_get_children: 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_get_children 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 nodespace_get_children 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_get_children. 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_get_children 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.