ons_upsert
AI agents use ons_upsert to create or update resources in Open Neural Substrate — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Open Neural Substrate environment.
Upsert operations are reversible writes that create or modify data records. In a knowledge graph context, this tool would add or update neuron entries, making it a Write risk. Severity is high because unauthorized upserts to a persistent knowledge graph could corrupt or poison the stored knowledge that Claude relies on.
From the tool's definition Tool name 'ons_upsert' (upsert = update or insert) and context as a knowledge graph management system indicates create/modify operations on persistent data. The sibling tools include ons_delete and ons_rewire, confirming this is a data mutation system.
Attacks that exploit this kind of access
ons_upsert. It is categorised as a Write tool in the Open Neural Substrate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Open Neural Substrate MCP server in PolicyLayer and add a rule for ons_upsert: 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 Open Neural Substrate. Nothing to install.
ons_upsert 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 ons_upsert 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 ons_upsert. 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.
ons_upsert is provided by the Open Neural Substrate MCP server (pedroknigge/open-neural-substrate). 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 →