scout_login · Scout MCP: Risk & Policy

WHAT IT DOES

What scout_login does on Scout

AI agents invoke scout_login to trigger actions in Scout. 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.

WHY IT NEEDS A POLICY

Why scout_login needs a policy

This tool executes an automated login flow on external social platforms (Twitter, LinkedIn, Instagram, Facebook), triggering multi-step authentication processes and persisting session state. It performs external operations (submitting credentials, handling challenges) whose effects depend on the arguments provided.

From the tool's definition Log in to a social platform automatically. Handles multi-step flows and unusual activity challenges. Auto-saves the session on success

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scout_login Rate-limited

scout_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "scout_login": {
      "limits": [
        {
          "counter": "scout_login_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about scout_login

What does the scout_login tool do? +

Log in to a social platform automatically. Handles multi-step flows and unusual activity challenges. Auto-saves the session on success (no need to call scout_save_session). Twitter accepts username; LinkedIn/Instagram/Facebook expect email. Returns {success, url, challenge_type?, error?} — always check success before proceeding. It is categorised as a Execute tool in the Scout MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scout_login? +

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

What risk level is scout_login? +

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

Can I rate-limit scout_login? +

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

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

scout_login is provided by the Scout MCP server (lautrek/scout). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.