send_connection_request
AI agents use send_connection_request to create or update resources in LinkedIn Intelligence MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LinkedIn Intelligence MCP Server environment.
Sending connection requests creates new social relationships and modifies LinkedIn profile state. This is reversible (connections can be removed) so it is Write rather than Destructive. Severity is medium because automated mass connection requests could damage professional reputation, trigger rate limiting, or violate LinkedIn terms of service if misused at scale by an AI agent.
From the tool's definition Tool name 'send_connection_request' indicates it creates a new connection relationship on LinkedIn. The server description mentions 'engagement automation' and 'messaging', confirming this tool modifies social graph state.
Documented attack patterns abuse exactly the kind of access send_connection_request gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn Intelligence MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send_connection_request:
{
"version": "1",
"default": "deny",
"tools": {
"send_connection_request": {
"limits": [
{
"counter": "send_connection_request_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
send_connection_request. It is categorised as a Write tool in the LinkedIn Intelligence MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LinkedIn Intelligence 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 Intelligence MCP Server. Nothing to install.
send_connection_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
send_connection_request is provided by the LinkedIn Intelligence MCP Server MCP server (southleft/linkedin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 87 LinkedIn Intelligence MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
87 LinkedIn Intelligence MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.