linkedin_get_profile
Get a LinkedIn user profile by ID, public identifier (vanity name), or profile URL. Returns name, headline, location, and other profile information.
This record as markdown: /tools/io-github-saloprj-dialogbrain/linkedin-get-profile.md
What linkedin_get_profile does on Dialogbrain
AI agents call linkedin_get_profile 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 |
|---|---|---|---|
identifier | string | Yes | LinkedIn member ID, public identifier (vanity name), or full profile URL |
Parameters from the server's own tool schema.
Why linkedin_get_profile is rated Low
This is a read operation that queries and retrieves publicly available or authorized LinkedIn profile data. There is no creation, modification, deletion, code execution, or financial transaction involved. The blast radius is low as the tool only returns existing profile information without capability to alter data or trigger external operations.
From the tool's definition Tool retrieves profile information from LinkedIn via 'Get a LinkedIn user profile by ID, public identifier (vanity name), or profile URL' with returns of 'name, headline, location, and other profile information'.
Attacks that exploit this kind of access
The rule that runs linkedin_get_profile 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_get_profile, this is the rule to start with:
linkedin_get_profile 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_get_profile call is checked against it from then on.
Questions about linkedin_get_profile
Get a LinkedIn user profile by ID, public identifier (vanity name), or profile URL. Returns name, headline, location, and other profile information. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
linkedin_get_profile accepts 1 parameter: identifier. Required: identifier. 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_get_profile: 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_get_profile 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_get_profile 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_get_profile. 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_get_profile 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