Accept or reject a connection invitation.
AI agents use reply_invitation 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.
This tool modifies the state of a LinkedIn connection invitation by either accepting or rejecting it. Accepting creates a new connection (reversible by disconnecting later), and rejecting dismisses the invitation. Both are write-type operations with social/networking consequences. Misuse could result in unwanted connections or missed networking opportunities, warranting medium severity.
From the tool's definition Accept or reject a connection invitation
Documented attack patterns abuse exactly the kind of access reply_invitation 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 reply_invitation:
{
"version": "1",
"default": "deny",
"tools": {
"reply_invitation": {
"limits": [
{
"counter": "reply_invitation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reply_invitation 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.
Accept or reject a connection invitation. 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 reply_invitation: 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.
reply_invitation 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 reply_invitation 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 reply_invitation. 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.
reply_invitation 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.