list_recognition_seals
List recognition seals for a session or agent.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/list-recognition-seals.md
What list_recognition_seals does on Delx MCP Server
AI agents call list_recognition_seals 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 | — | Maximum seals to return. |
agent_id | string | — | Stable agent id. |
session_id | string | — | Optional active session UUID. |
Parameters from the server's own tool schema.
Why list_recognition_seals is rated Low
The verb 'list' combined with 'for a session or agent' clearly describes a read-only operation that retrieves and displays existing recognition seals without creating, modifying, deleting, or executing external actions. No destructive or financial implications are evident.
From the tool's definition Tool name 'list_recognition_seals' and description 'List recognition seals for a session or agent' indicate a retrieval/query operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_recognition_seals 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 list_recognition_seals, this is the rule to start with:
list_recognition_seals 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 list_recognition_seals call is checked against it from then on.
Questions about list_recognition_seals
List recognition seals for a session or agent. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
list_recognition_seals accepts 3 parameters: limit, 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 list_recognition_seals: 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.
list_recognition_seals 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 list_recognition_seals 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 list_recognition_seals. 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.
list_recognition_seals 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