auth_linkedin · Lightpaper MCP: Risk & Policy

WHAT IT DOES

What auth_linkedin does on Lightpaper Mcp

AI agents invoke auth_linkedin to trigger actions in Lightpaper Mcp. 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 auth_linkedin needs a policy

This tool executes an external OAuth authentication process, which is a side-effecting operation that triggers external service interactions. However, the blast radius is low because it only initiates a standard OAuth flow without access to sensitive data or ability to modify account state directly. Severity is low because OAuth authorization is a benign, user-initiated operation.

From the tool's definition Tool initiates LinkedIn OAuth flow by returning an authorization URL. OAuth is an external operation that triggers authentication state changes and credential exchange outside the application.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

auth_linkedin Rate-limited

auth_linkedin 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": {
    "auth_linkedin": {
      "limits": [
        {
          "counter": "auth_linkedin_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 Lightpaper Mcp, so you can run agents against it safely.

FAQ

Questions about auth_linkedin

What does the auth_linkedin tool do? +

Start LinkedIn OAuth for login/signup. Returns an authorization URL for the user to open. It is categorised as a Execute tool in the Lightpaper Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on auth_linkedin? +

Register the Lightpaper MCP server in PolicyLayer and add a rule for auth_linkedin: 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_linkedin? +

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

Can I rate-limit auth_linkedin? +

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

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

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