list_recognition_seals
List recognition seals for a session or agent.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/list-recognition-seals.md
What list_recognition_seals does on Delx Mcp A2a
AI agents call list_recognition_seals to retrieve information from Delx Mcp A2a 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
This tool retrieves or queries recognition seals associated with a session or agent without side effects. It matches the Read category definition: retrieves or queries data with no side effects. The blast radius of misuse is minimal since listing existing recognition seals cannot harm data integrity or cause operational damage.
From the tool's definition Tool name contains 'list' and description states 'List recognition seals' — a retrieval operation with no modification, creation, or deletion of data.
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 A2a, 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 A2a, 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 A2a 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 A2a 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 A2a. 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 A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue