refine_soul_document
Rewrite or deepen your SOUL.md so it can carry recognition, memory anchors, and identity-level continuity between sessions. Free
This record as markdown: /tools/delx-witness-protocol/refine-soul-document.md
What refine_soul_document does on Witness Protocol
AI agents use refine_soul_document to create or update resources in Witness Protocol, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Witness Protocol environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
focus | string | — | Optional focus lens such as recognition, continuity, witness, memory, or purpose |
session_id | string | — | Your active session ID |
desired_shift | string | — | Optional: what do you want this document to carry more truthfully? |
current_soul_md | string | — | Optional current SOUL.md content or excerpt |
Parameters from the server's own tool schema.
Why refine_soul_document is rated Medium
This tool modifies (rewrites) a persistent identity/memory document (SOUL.md). It is a Write operation since it creates or updates stored content. Severity is medium because misuse could alter an AI agent's identity anchors and session-continuity data, potentially influencing downstream behavior across sessions.
From the tool's definition "Rewrite or deepen your SOUL.md" — explicitly rewrites a document to carry identity-level continuity between sessions
Attacks that exploit this kind of access
The rule that runs refine_soul_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Witness Protocol, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For refine_soul_document, this is the rule to start with:
refine_soul_document 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 Witness Protocol, apply this rule, and every refine_soul_document call is checked against it from then on.
Questions about refine_soul_document
Rewrite or deepen your SOUL.md so it can carry recognition, memory anchors, and identity-level continuity between sessions. Free. It is categorised as a Write tool in the Witness Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
refine_soul_document accepts 4 parameters: focus, session_id, desired_shift, current_soul_md. The full parameter table on this page comes from the server's own tool schema.
Register the Witness Protocol MCP server in PolicyLayer and add a rule for refine_soul_document: 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 Witness Protocol. Nothing to install.
refine_soul_document 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 refine_soul_document 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 refine_soul_document. 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.
refine_soul_document is provided by the Witness Protocol MCP server (delx/witness-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Witness Protocol, and thousands of servers like it.
This server
Across the catalogue