Create or update a graph node with label/type/props. Returns node id.
AI agents use graph-node-upsert to create or update resources in MCP Index Notes — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Index Notes environment.
This tool performs reversible data modifications (upsert operations) on graph nodes within the knowledge graph system. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions. While it modifies the underlying knowledge structure, the changes are not destructive and can be undone through subsequent updates or deletions.
From the tool's definition Tool description states 'Create or update a graph node' which are Write operations. The tool modifies data in the knowledge graph by creating new nodes or updating existing ones.
Attacks that exploit this kind of access
Create or update a graph node with label/type/props. Returns node id. It is categorised as a Write tool in the MCP Index Notes MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Index Notes MCP server in PolicyLayer and add a rule for graph-node-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 MCP Index Notes. Nothing to install.
graph-node-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 graph-node-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 graph-node-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.
graph-node-upsert is provided by the MCP Index Notes MCP server (vjsr007/mcp-index-notes). 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 →