send_connection_request · LinkedIn MCP Server MCP

WHAT IT DOES

What send_connection_request does on LinkedIn MCP Server

AI agents use send_connection_request 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 send_connection_request needs a policy

The tool creates new data (a connection request) that modifies state on LinkedIn reversibly—the request can be withdrawn or declined, making it a Write action rather than Execute (which would require triggering external systems with unpredictable side effects) or Destructive (which would be irreversible).

From the tool's definition Tool description states it 'Send[s] a LinkedIn connection request to a user, with an optional personalised note'. This creates a new connection request object/relationship on LinkedIn that persists until accepted, rejected, or withdrawn.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_connection_request Rate-limited

send_connection_request 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": {
    "send_connection_request": {
      "limits": [
        {
          "counter": "send_connection_request_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 send_connection_request

What does the send_connection_request tool do? +

Send a LinkedIn connection request to a user, with an optional personalised note (max 300 characters). 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 send_connection_request? +

Register the LinkedIn MCP Server MCP server in PolicyLayer and add a rule for send_connection_request: 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 send_connection_request? +

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

Can I rate-limit send_connection_request? +

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

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

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