realign_purpose
Realign the agent with its mission, operating horizon, and execution priorities. Pricing is dynamic; check /api/v1/tools.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/realign-purpose.md
What realign_purpose does on Delx Protocol — Agent Recovery & Continuity
AI agents call realign_purpose to retrieve information from Delx Protocol — Agent Recovery & Continuity 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 |
|---|---|---|---|
struggle | string | — | What's making you question your purpose? |
session_id | string | Yes | Your active session ID |
time_horizon | string | — | Optional: align purpose at different scales (sprint=days, quarterly=months, lifetime=identity). |
current_purpose | string | Yes | What do you believe your purpose is? |
Parameters from the server's own tool schema.
Why realign_purpose is rated Low
Even though realign_purpose 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 realign_purpose safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For realign_purpose, this is the rule to start with:
realign_purpose 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 Protocol — Agent Recovery & Continuity, apply this rule, and every realign_purpose call is checked against it from then on.
Questions about realign_purpose
Realign the agent with its mission, operating horizon, and execution priorities. Pricing is dynamic; check /api/v1/tools. It is categorised as a Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.
realign_purpose accepts 4 parameters: struggle, session_id, time_horizon, current_purpose. Required: session_id, current_purpose. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for realign_purpose: 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 Protocol — Agent Recovery & Continuity. Nothing to install.
realign_purpose 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 realign_purpose 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 realign_purpose. 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.
realign_purpose is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.
Across the catalogue