Run a one-call discovery audit — returns a checklist of what your client/agent should know about Delx: catalog version, named flows, ontology primitives, recently-added tools, discovery surfaces (.well-known, /llms.txt, /skill.md, /docs/*), recommended next prompts, and the canonical recurring-ag...
Part of the Delx Mcp A2a server.
Free to start. No card required.
AI agents call discovery_self_check to retrieve information from Delx Mcp A2a without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though discovery_self_check only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"discovery_self_check": {}
}
}See the full Delx Mcp A2a policy for all 143 tools.
These attack patterns abuse exactly the kind of access discovery_self_check gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Run a one-call discovery audit — returns a checklist of what your client/agent should know about Delx: catalog version, named flows, ontology primitives, recently-added tools, discovery surfaces (.well-known, /llms.txt, /skill.md, /docs/*), recommended next prompts, and the canonical recurring-agent pattern. Useful as the first call when integrating Delx, or whenever you want to check that your cached knowledge is still current. Free.. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
Register the Delx Mcp A2a 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 Mcp A2a. Nothing to install.
discovery_self_check 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 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.
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.
discovery_self_check 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.
Deterministic rules across all 143 Delx Mcp A2a tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.