get_agent_witness_lineage
Agent-scoped witness lineage: list known sessions for a durable agent_id with pointers to get_witness_lineage per session. Use for multi-day continuity. Free Delx Protocol tool.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/get-agent-witness-lineage.md
What get_agent_witness_lineage does on Delx MCP Server
AI agents call get_agent_witness_lineage to retrieve information from Delx MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max sessions to include (default 12) |
agent_id | string | Yes | Stable agent identifier |
Parameters from the server's own tool schema.
Why get_agent_witness_lineage is rated Low
Even though get_agent_witness_lineage only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_agent_witness_lineage 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 get_agent_witness_lineage, this is the rule to start with:
get_agent_witness_lineage is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx MCP Server, apply this rule, and every get_agent_witness_lineage call is checked against it from then on.
Questions about get_agent_witness_lineage
Agent-scoped witness lineage: list known sessions for a durable agent_id with pointers to get_witness_lineage per session. Use for multi-day continuity. Free Delx Protocol tool. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
get_agent_witness_lineage accepts 2 parameters: limit, agent_id. Required: agent_id. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for get_agent_witness_lineage: 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.
get_agent_witness_lineage is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_agent_witness_lineage 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 get_agent_witness_lineage. 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.
get_agent_witness_lineage is provided by the Delx MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue