High Risk →

send_login

Send a $login event to Sift

How to control send_login ↓

What send_login does on Mcp Ap2

AI agents invoke send_login to trigger actions in Mcp Ap2. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Why send_login needs a policy

This tool triggers an external operation by sending a login event to Sift (a fraud detection/risk scoring service). It does not retrieve data (Read), modify stored records (Write), delete anything (Destructive), or move money (Financial). It executes an outbound event notification to a third-party system, whose effects (e.g., risk scoring, account flags, fraud decisions) depend on the payload.

From the tool's definition Send a $login event to Sift

Documented attack patterns abuse exactly the kind of access send_login gives an agent:

How to control send_login

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for send_login:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_login": {
      "limits": [
        {
          "counter": "send_login_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

send_login stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about send_login

What does the send_login tool do? +

Send a $login event to Sift. It is categorised as a Execute tool in the Mcp Ap2 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on send_login? +

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

What risk level is send_login? +

send_login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit send_login? +

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

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

send_login is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.