linkedin_list_invitations_sent

List your pending sent connection invitations on LinkedIn.

SERVERDialogbrain SOURCEhttps://api.dialogbrain.com/mcp
Low RISK CLASS
Category Read
Parameters 20 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-saloprj-dialogbrain/linkedin-list-invitations-sent.md

What linkedin_list_invitations_sent does on Dialogbrain

AI agents call linkedin_list_invitations_sent to retrieve information from Dialogbrain without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
limit integer Maximum invitations to return
cursor string Pagination cursor from previous response

Parameters from the server's own tool schema.

Why linkedin_list_invitations_sent is rated Low

This tool only retrieves and displays existing invitation data from LinkedIn. It does not create, modify, delete, or execute any actions. The operation is read-only with no reversible or irreversible changes to state. Severity is low because the information returned is metadata about the user's own outgoing invitations, with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name includes 'list' and description states 'List your pending sent connection invitations' — this is a query operation that retrieves data without modification or side effects.

Questions about linkedin_list_invitations_sent

What does the linkedin_list_invitations_sent tool do? +

List your pending sent connection invitations on LinkedIn. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.

What parameters does linkedin_list_invitations_sent accept? +

linkedin_list_invitations_sent accepts 2 parameters: limit, cursor. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on linkedin_list_invitations_sent? +

Register the Dialogbrain MCP server in PolicyLayer and add a rule for linkedin_list_invitations_sent: 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.

What risk level is linkedin_list_invitations_sent? +

linkedin_list_invitations_sent is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit linkedin_list_invitations_sent? +

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

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

linkedin_list_invitations_sent 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Dialogbrain's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.