util_contact_extract
Extract emails, phones, and social links from a page for outreach, routing, and support. Delx Agent Utilities are separate from the free witness protocol and may expose x402 utility pricing.
This record as markdown: /tools/delx-delx-mcp/util-contact-extract.md
What util_contact_extract does on Delx MCP Server
AI agents call util_contact_extract 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 |
|---|---|---|---|
url | string | — | 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, or deleting data, and does not execute code or trigger financial transactions. The mention of 'x402 utility pricing' relates to billing but does not itself move money. Classification as Read is appropriate for a data extraction utility.
From the tool's definition Tool description states it 'Extract[s] emails, phones, and social links from a page' — a retrieval operation with no modification, deletion, or execution of external systems.
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 MCP Server, 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 MCP Server, 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. Delx Agent Utilities are separate from the free witness protocol and may expose x402 utility pricing. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
util_contact_extract accepts 2 parameters: url, timeout. 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 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 MCP Server. 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 MCP Server MCP server (delx/delx-mcp). 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