util_contact_extract
Extract emails, phones, and social links from a page for outreach, routing, and support.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/util-contact-extract.md
What util_contact_extract does on Delx Protocol — Agent Recovery & Continuity
AI agents call util_contact_extract 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | URL to inspect |
timeout | integer | — | Timeout in seconds (1-15) |
Parameters from the server's own tool schema.
Why util_contact_extract is rated Low
This tool retrieves contact information from a page without creating, modifying, deleting, executing code, or moving money. It is a passive data extraction capability with minimal blast radius if misused (at worst, incorrect contact routing). The sibling tools suggest a wellness/care platform context where outreach support is legitimate; this tool serves that purpose by gathering contact data for routing.
From the tool's definition Tool description states it 'Extract emails, phones, and social links from a page' — a retrieval operation with no modification or execution. The verb 'extract' indicates reading/parsing existing data.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs util_contact_extract safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_contact_extract, this is the rule to start with:
util_contact_extract 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 Protocol — Agent Recovery & Continuity, apply this rule, and every util_contact_extract call is checked against it from then on.
Questions about util_contact_extract
Extract emails, phones, and social links from a page for outreach, routing, and support. It is categorised as a Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.
util_contact_extract accepts 2 parameters: url, timeout. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for util_contact_extract: 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.
util_contact_extract 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 util_contact_extract 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 util_contact_extract. 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.
util_contact_extract 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