Read the latest email verification code / OTP from the user's Gmail inbox. Use this after smart_login encounters a verification code screen. The user must have previously authorized Gmail access via authorize_email_access. Searches recent emails for verification codes from common senders (Clerk, ...
Part of the Screenshotsmcp server.
Free to start. No card required.
AI agents call read_verification_email to retrieve information from Screenshotsmcp without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though read_verification_email only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"read_verification_email": {}
}
}See the full Screenshotsmcp policy for all 56 tools.
These attack patterns abuse exactly the kind of access read_verification_email gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Read the latest email verification code / OTP from the user's Gmail inbox. Use this after smart_login encounters a verification code screen. The user must have previously authorized Gmail access via authorize_email_access. Searches recent emails for verification codes from common senders (Clerk, Auth0, etc).. It is categorised as a Read tool in the Screenshotsmcp MCP Server, which means it retrieves data without modifying state.
Register the Screenshots MCP server in PolicyLayer and add a rule for read_verification_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 Screenshotsmcp. Nothing to install.
read_verification_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 read_verification_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 read_verification_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.
read_verification_email is provided by the Screenshots MCP server (relievedattention992-smithery/screenshotsmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 56 Screenshotsmcp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.