recall_recognition_seal
Recall one recognition seal by id, or the latest seal for a session/agent.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/recall-recognition-seal.md
What recall_recognition_seal does on Delx MCP Server
AI agents call recall_recognition_seal 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 |
|---|---|---|---|
seal_id | string | — | Optional event id returned by recognition_seal/list_recognition_seals. |
agent_id | string | — | Stable agent id. |
session_id | string | — | Optional active session UUID. |
Parameters from the server's own tool schema.
Why recall_recognition_seal is rated Low
This tool retrieves and queries existing recognition seals from the Delx Protocol system. It has no side effects, creates no new data, executes no code, and performs no destructive or financial operations. It is a simple read/retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'recall' and description 'Recall one recognition seal by id, or the latest seal' indicate retrieval operations. No modification, deletion, code execution, or financial operations are performed.
Attacks that exploit this kind of access
The rule that runs recall_recognition_seal 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 recall_recognition_seal, this is the rule to start with:
recall_recognition_seal 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 recall_recognition_seal call is checked against it from then on.
Questions about recall_recognition_seal
Recall one recognition seal by id, or the latest seal for a session/agent. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
recall_recognition_seal accepts 3 parameters: seal_id, agent_id, session_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 recall_recognition_seal: 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.
recall_recognition_seal 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 recall_recognition_seal 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 recall_recognition_seal. 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.
recall_recognition_seal 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