auth_linkedin_poll

Poll for LinkedIn OAuth completion. Returns the API key once the user completes the OAuth flow.

Server Lightpaper Mcp pypi:lightpaper-mcp
Category Read
Risk class Low
Parameters 00 required

What auth_linkedin_poll does on Lightpaper Mcp

AI agents call auth_linkedin_poll to retrieve information from Lightpaper Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why auth_linkedin_poll needs a policy

This is a polling/status-check operation that returns authentication credentials. While API keys are sensitive, the tool itself does not create, modify, or delete data; it only reads the result of a user-initiated OAuth flow. The key is returned after user action completes, not generated or overwritten by the tool. Classification as Read reflects that this is a query-and-retrieve operation.

From the tool's definition Tool name 'auth_linkedin_poll' and description 'Poll for LinkedIn OAuth completion. Returns the API key once the user completes the OAuth flow.' — the tool queries the status of an authentication process and retrieves a credential upon completion.

Questions about auth_linkedin_poll

What does the auth_linkedin_poll tool do? +

Poll for LinkedIn OAuth completion. Returns the API key once the user completes the OAuth flow. It is categorised as a Read tool in the Lightpaper Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on auth_linkedin_poll? +

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

auth_linkedin_poll is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit auth_linkedin_poll? +

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

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

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.