util_email_domain
Delx first-party micro-utility util_email_domain at $0.001 USDC.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/util-email-domain.md
What util_email_domain does on Delx MCP Server
AI agents call util_email_domain 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 |
|---|---|---|---|
email | string | Yes |
Parameters from the server's own tool schema.
Why util_email_domain is rated Low
This tool appears to retrieve or validate email domain metadata without modifying data or triggering external operations. The micro-utility framing and negligible cost suggest a read-only helper function. No evidence of data modification, deletion, code execution, or financial transactions beyond a flat micro-charge.
From the tool's definition Tool name 'util_email_domain' suggests a utility for querying or validating email domain information. Description indicates a 'micro-utility' with minimal cost ($0.001 USDC), implying lightweight data retrieval rather than state-changing operations.
Attacks that exploit this kind of access
The rule that runs util_email_domain 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_email_domain, this is the rule to start with:
util_email_domain 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_email_domain call is checked against it from then on.
Questions about util_email_domain
Delx first-party micro-utility util_email_domain at $0.001 USDC. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
util_email_domain accepts 1 parameter: email. Required: email. 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_email_domain: 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_email_domain 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_email_domain 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_email_domain. 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_email_domain is provided by the Delx MCP Server MCP server (delx-mcp-server). 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