connect_with_person · LinkedIn MCP Server MCP: Risk & Policy

WHAT IT DOES

What connect_with_person does on LinkedIn MCP Server

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

WHY IT NEEDS A POLICY

Why connect_with_person needs a policy

This tool creates a new connection request on LinkedIn, which is a reversible action (requests can be withdrawn, connections removed). It modifies user data and network state but is not destructive (deletions are separate operations). No financial transaction occurs. The high severity reflects that mass automated connection requests could constitute spam, violate LinkedIn terms, or manipulate professional networks.

From the tool's definition Tool name is 'connect_with_person' on a LinkedIn MCP server that performs 'authenticated browser automation.' Connection requests on LinkedIn are social/professional relationship modifications that alter the platform state and sender's outbound network.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_with_person Rate-limited

connect_with_person 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": {
    "connect_with_person": {
      "limits": [
        {
          "counter": "connect_with_person_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 LinkedIn MCP Server, so you can run agents against it safely.

FAQ

Questions about connect_with_person

What does the connect_with_person tool do? +

connect_with_person. It is categorised as a Write tool in the LinkedIn MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on connect_with_person? +

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

What risk level is connect_with_person? +

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

Can I rate-limit connect_with_person? +

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

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

connect_with_person is provided by the LinkedIn MCP Server MCP server (stickerdaniel/linkedin-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.