request_magic_link · Run402 MCP: Risk & Policy

WHAT IT DOES

What request_magic_link does on Run402

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

WHY IT NEEDS A POLICY

Why request_magic_link needs a policy

This tool creates new user accounts and triggers email delivery, which are both write operations. It is reversible (users can be removed), so it does not meet the Destructive threshold. The rate limiting (5/hr per email, per-project by tier) indicates awareness of abuse potential but does not prevent misuse by a compromised agent.

From the tool's definition Tool description states it 'Send[s] a passwordless login email (magic link) to a project user. Auto-creates the user on first verification.' This creates user accounts (reversible via deletion/deactivation) and sends emails with side effects on first…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

request_magic_link Rate-limited

request_magic_link 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": {
    "request_magic_link": {
      "limits": [
        {
          "counter": "request_magic_link_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 Run402, so you can run agents against it safely.

FAQ

Questions about request_magic_link

What does the request_magic_link tool do? +

Send a passwordless login email (magic link) to a project user. Auto-creates the user on first verification. Rate limited per email (5/hr) and per project (by tier). It is categorised as a Write tool in the Run402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on request_magic_link? +

Register the Run402 MCP server in PolicyLayer and add a rule for request_magic_link: 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 Run402. Nothing to install.

What risk level is request_magic_link? +

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

Can I rate-limit request_magic_link? +

Yes. Add a rate_limit block to the request_magic_link 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 request_magic_link completely? +

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

request_magic_link is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.