linkedin_list_connections
List your LinkedIn connections, sorted by most recently added.
This record as markdown: /tools/io-github-saloprj-dialogbrain/linkedin-list-connections.md
What linkedin_list_connections does on Dialogbrain
AI agents call linkedin_list_connections 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Maximum connections to return |
cursor | string | — | Pagination cursor from previous response |
Parameters from the server's own tool schema.
Why linkedin_list_connections is rated Low
This tool retrieves LinkedIn connection data in a read-only manner. It has no side effects, does not modify data, execute external operations, or access financial systems. The blast radius of misuse is minimal—an attacker could enumerate the user's professional network but cannot alter it or cause irreversible harm.
From the tool's definition Tool name 'linkedin_list_connections' and description 'List your LinkedIn connections' indicate data retrieval with no modification. The verb 'list' is a classic Read operation that queries and returns existing data.
Attacks that exploit this kind of access
The rule that runs linkedin_list_connections 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_list_connections, this is the rule to start with:
linkedin_list_connections is read-only, so it stays allowed. 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_list_connections call is checked against it from then on.
Questions about linkedin_list_connections
List your LinkedIn connections, sorted by most recently added. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
linkedin_list_connections accepts 2 parameters: limit, cursor. 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_list_connections: 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_list_connections is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the linkedin_list_connections 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_list_connections. 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_list_connections 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