auth_email · Lightpaper MCP: Risk & Policy

WHAT IT DOES

What auth_email does on Lightpaper Mcp

AI agents use auth_email to create or update resources in Lightpaper Mcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lightpaper Mcp environment.

WHY IT NEEDS A POLICY

Why auth_email needs a policy

This tool writes data (sends a code) but has minimal side effects. It doesn't delete, execute arbitrary operations, or move money. The blast radius of misuse is low—an attacker could spam verification emails or harass a user, but cannot access accounts or cause data loss. Classified as Write rather than Execute because it's a straightforward messaging action, not code/command execution.

From the tool's definition "Send a 6-digit verification code to the user" - this action creates and delivers a verification code, modifying the authentication state by initiating a verification flow.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

auth_email Rate-limited

auth_email stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "auth_email": {
      "limits": [
        {
          "counter": "auth_email_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Lightpaper Mcp, so you can run agents against it safely.

FAQ

Questions about auth_email

What does the auth_email tool do? +

Send a 6-digit verification code to the user. It is categorised as a Write tool in the Lightpaper Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on auth_email? +

Register the Lightpaper MCP server in PolicyLayer and add a rule for auth_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 Lightpaper Mcp. Nothing to install.

What risk level is auth_email? +

auth_email is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit auth_email? +

Yes. Add a rate_limit block to the auth_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.

How do I block auth_email completely? +

Set action: deny in the PolicyLayer policy for auth_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.

What MCP server provides auth_email? +

auth_email is provided by the Lightpaper MCP server (pypi:lightpaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.