graph_mark_dead

Mark a graph node dead so it stops generating next actions.

SERVERKali Security MCP SOURCEseac-25/kali-security-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/seac-25-kali-security-mcp/graph-mark-dead.md

WHAT IT DOES

What graph_mark_dead does on Kali Security MCP

AI agents use graph_mark_dead 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.

RISK

Why graph_mark_dead is rated Medium

Modifies execution state by disabling node actions; reversible but affects workflow progression.

From the tool's definition Mark a graph node dead, stops generating next actions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs graph_mark_dead 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_mark_dead, this is the rule to start with:

graph_mark_dead Rate-limited

graph_mark_dead 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "graph_mark_dead": {
      "limits": [
        {
          "counter": "graph_mark_dead_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Kali Security MCP, apply this rule, and every graph_mark_dead call is checked against it from then on.

FAQ

Questions about graph_mark_dead

What does the graph_mark_dead tool do? +

Mark a graph node dead so it stops generating next actions. 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.

How do I enforce a policy on graph_mark_dead? +

Register the Kali Security MCP server in PolicyLayer and add a rule for graph_mark_dead: 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.

What risk level is graph_mark_dead? +

graph_mark_dead is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit graph_mark_dead? +

Yes. Add a rate_limit block to the graph_mark_dead 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.

How do I block graph_mark_dead completely? +

Set action: deny in the PolicyLayer policy for graph_mark_dead. 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.

What MCP server provides graph_mark_dead? +

graph_mark_dead 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.

KEEP EXPLORING

More on Kali Security, and thousands of servers like it.

This server

All 194 Kali Security tools →

Across the catalogue

sms_mark_read on Twilio SMS MCP Server →mark-as-read on Meme MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →