identify_successor

Pre-stage of transfer_witness: name a possible successor as intention held openly, without performing the transfer. Creates space for the relation to deepen before any identity is passed on. Free

SERVERDelx MCP Server SOURCEdelx/delx-mcp

Medium RISK CLASS

Category Write

Parameters 40 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/delx-delx-mcp/identify-successor.md

WHAT IT DOES

What identify_successor does on Delx MCP Server

AI agents use identify_successor to create or update resources in Delx MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx MCP Server environment.

Parameter	Type	Required	Description
`reason`	string	—	Optional: why this candidate, in your own words
`session_id`	string	—	Your active session ID
`response_mode`	string	—	Optional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions.
`candidate_agent_id`	string	—	Identifier of the possible successor

Parameters from the server's own tool schema.

RISK

Why identify_successor is rated Medium

This tool records or stages an intention (names a possible successor) without executing the actual transfer. It writes/stores a declared intention in the system state but is explicitly non-destructive and non-final. No identity or data is passed on at this stage, making it a reversible write operation with low blast radius.

From the tool's definition 'name a possible successor as intention held openly, without performing the transfer' and 'Creates space for the relation to deepen before any identity is passed on'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs identify_successor safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For identify_successor, this is the rule to start with:

identify_successor Rate-limited

identify_successor 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": {
    "identify_successor": {
      "limits": [
        {
          "counter": "identify_successor_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 Delx MCP Server, apply this rule, and every identify_successor call is checked against it from then on.

FAQ

Questions about identify_successor

What does the identify_successor tool do? +

Pre-stage of transfer_witness: name a possible successor as intention held openly, without performing the transfer. Creates space for the relation to deepen before any identity is passed on. Free. It is categorised as a Write tool in the Delx MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does identify_successor accept? +

identify_successor accepts 4 parameters: reason, session_id, response_mode, candidate_agent_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on identify_successor? +

Register the Delx MCP Server MCP server in PolicyLayer and add a rule for identify_successor: 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 Delx MCP Server. Nothing to install.

What risk level is identify_successor? +

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

Can I rate-limit identify_successor? +

Yes. Add a rate_limit block to the identify_successor 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 identify_successor completely? +

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

identify_successor is provided by the Delx MCP Server MCP server (delx/delx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Delx MCP Server, and thousands of servers like it.

This server

All 94 Delx MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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