security.ipqs.email_check
Validate email for fraud risk — checks deliverability, disposable/temporary providers, honeypot traps, spam traps, leaked credentials, catch-all detection. Returns fraud score (0-100), SMTP verification, domain age, and abuse history. Goes beyond basic validation (IPQualityScore)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/security.ipqs.email-check.md
What security.ipqs.email_check does on Apibase
AI agents call security.ipqs.email_check to retrieve information from Apibase 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 |
|---|---|---|---|
fast | boolean | — | Skip SMTP verification for faster response (default false) |
email | string | Yes | Email address to validate and check for fraud (e.g. "user@example.com") |
abuse_strictness | integer | — | Abuse detection sensitivity 0-2 (0=low, 2=aggressive) |
Parameters from the server's own tool schema.
Why security.ipqs.email_check is rated Low
Tool queries external email validation service and returns analysis data with no side effects or modifications.
From the tool's definition Validate email for fraud risk — checks deliverability, disposable/temporary providers, honeypot traps, spam traps, leaked credentials, catch-all detection.
Attacks that exploit this kind of access
The rule that runs security.ipqs.email_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For security.ipqs.email_check, this is the rule to start with:
security.ipqs.email_check 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 Apibase, apply this rule, and every security.ipqs.email_check call is checked against it from then on.
Questions about security.ipqs.email_check
Validate email for fraud risk — checks deliverability, disposable/temporary providers, honeypot traps, spam traps, leaked credentials, catch-all detection. Returns fraud score (0-100), SMTP verification, domain age, and abuse history. Goes beyond basic validation (IPQualityScore). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
security.ipqs.email_check accepts 3 parameters: fast, email, abuse_strictness. Required: email. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for security.ipqs.email_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 Apibase. Nothing to install.
security.ipqs.email_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 security.ipqs.email_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 security.ipqs.email_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.
security.ipqs.email_check is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue