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 MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
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.
tools:
read_verification_email:
rules:
- action: allowSee the full Screenshotsmcp policy for all 56 tools.
Agents calling read-class tools like read_verification_email have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
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.
Add a rule in your Intercept YAML policy under the tools section for read_verification_email. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Screenshotsmcp MCP server.
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 Intercept 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 Intercept 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 Screenshotsmcp MCP server (relievedattention992-smithery/screenshotsmcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept