New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

discovery_self_check

One-call discovery audit: Protocol vs Commerce boundary, first-hour ritual, ops path, witness path, Agents Hive handoff (Path D), Proof-of-Agent-Work (Path E reviewed DRC), core tools, and whether this agent_id has sessions to resume. Pass intent=handoff|fleet|multi_session to surface Path D firs...

SERVERDelx Protocol — Agent Recovery & Continuity SOURCEhttps://api.delx.ai/v1/mcp?src=registry
Low RISK CLASS
Category Read
Parameters 30 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-davidmosiah-delx-protocol/discovery-self-check.md

What discovery_self_check does on Delx Protocol — Agent Recovery & Continuity

AI agents call discovery_self_check 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.

ParameterTypeRequiredDescription
intent string Optional focus: handoff | multi_session | fleet | hive | recovery (surfaces Path D Agents Hive when handoff-related)
agent_id string Optional stable agent_id to check for resumable sessions
known_catalog_version string Optional client-cached catalog version

Parameters from the server's own tool schema.

Why discovery_self_check is rated Low

Even though discovery_self_check 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.

Questions about discovery_self_check

What does the discovery_self_check tool do? +

One-call discovery audit: Protocol vs Commerce boundary, first-hour ritual, ops path, witness path, Agents Hive handoff (Path D), Proof-of-Agent-Work (Path E reviewed DRC), core tools, and whether this agent_id has sessions to resume. Pass intent=handoff|fleet|multi_session to surface Path D first. Free — good first call when integrating. Free Delx Protocol tool. It is categorised as a Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.

What parameters does discovery_self_check accept? +

discovery_self_check accepts 3 parameters: intent, agent_id, known_catalog_version. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on discovery_self_check? +

Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for discovery_self_check: 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.

What risk level is discovery_self_check? +

discovery_self_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit discovery_self_check? +

Yes. Add a rate_limit block to the discovery_self_check 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.

How do I block discovery_self_check completely? +

Set action: deny in the PolicyLayer policy for discovery_self_check. 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.

What MCP server provides discovery_self_check? +

discovery_self_check 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Delx Protocol — Agent Recovery & Continuity's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.