Analyze an email for phishing indicators. Checks sender domain, email headers (SPF/DKIM/DMARC), brand impersonation, embedded URLs and phone numbers. Returns unified risk score with detailed header and sender analysis.
AI agents call check_email to retrieve information from ScamVerify without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries an email against threat intelligence databases to detect phishing indicators and return analysis results. It performs no side effects, does not execute code or commands, does not modify or delete data, and does not involve financial transactions. It is a read-only inspection tool that matches the 'Read' category: retrieves or queries data with no side effects.
From the tool's definition Tool 'check_email' analyzes and returns risk scores and analysis results without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
Analyze an email for phishing indicators. Checks sender domain, email headers (SPF/DKIM/DMARC), brand impersonation, embedded URLs and phone numbers. Returns unified risk score with detailed header and sender analysis. It is categorised as a Read tool in the ScamVerify MCP Server, which means it retrieves data without modifying state.
Register the ScamVerify MCP server in PolicyLayer and add a rule for check_email: 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 ScamVerify. Nothing to install.
check_email 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 check_email 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 check_email. 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.
check_email is provided by the ScamVerify MCP server (scamverifyai/scamverify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →