linkedin_invite
Send a connection invitation to a LinkedIn user. Optionally include a personalized message (max 300 characters). Rate limited: LinkedIn allows 80-100 invitations per day, max 200 per week.
This record as markdown: /tools/io-github-saloprj-dialogbrain/linkedin-invite.md
What linkedin_invite does on Dialogbrain
AI agents use linkedin_invite to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
message | string | — | Optional personalized invitation message (max 300 characters) |
provider_id | string | Yes | LinkedIn provider ID of the person to invite (from search results or profile) |
Parameters from the server's own tool schema.
Why linkedin_invite is rated Medium
This tool creates/sends data (connection invitation) but does not delete, execute code, move money, or trigger irreversible changes. The action is reversible—the invitation can be declined or withdrawn. Rate limiting context confirms it's a controlled write operation rather than a destructive or dangerous action.
From the tool's definition Tool description states 'Send a connection invitation to a LinkedIn user' with optional personalized message. This is a write operation that creates a new connection request object in LinkedIn's system.
Attacks that exploit this kind of access
The rule that runs linkedin_invite safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linkedin_invite, this is the rule to start with:
linkedin_invite 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every linkedin_invite call is checked against it from then on.
Questions about linkedin_invite
Send a connection invitation to a LinkedIn user. Optionally include a personalized message (max 300 characters). Rate limited: LinkedIn allows 80-100 invitations per day, max 200 per week. It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
linkedin_invite accepts 2 parameters: message, provider_id. Required: provider_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for linkedin_invite: 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 Dialogbrain. Nothing to install.
linkedin_invite 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 linkedin_invite 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 linkedin_invite. 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.
linkedin_invite is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue