graph_upsert
Upsert a graph node. next_checks is comma-separated. meta_json is optional JSON object.
This record as markdown: /tools/seac-25-kali-security-mcp/graph-upsert.md
What graph_upsert does on Kali Security MCP
AI agents use graph_upsert to create or update resources in Kali Security MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kali Security MCP environment.
Why graph_upsert is rated Medium
Creates or modifies graph data reversibly in what appears to be a knowledge/results tracking system.
From the tool's definition Upsert a graph node with optional JSON metadata
Attacks that exploit this kind of access
The rule that runs graph_upsert safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kali Security MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For graph_upsert, this is the rule to start with:
graph_upsert 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 Kali Security MCP, apply this rule, and every graph_upsert call is checked against it from then on.
Questions about graph_upsert
Upsert a graph node. next_checks is comma-separated. meta_json is optional JSON object. It is categorised as a Write tool in the Kali Security MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kali Security MCP server in PolicyLayer and add a rule for graph_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 Kali Security MCP. Nothing to install.
graph_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_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_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_upsert is provided by the Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kali Security, and thousands of servers like it.
This server
Across the catalogue