Get a LinkedIn user profile summary including name, headline, location, about section, experience, and education. Defaults to the currently logged-in user
AI agents call get_profile to retrieve information from LinkedIn MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns user profile information without creating, modifying, deleting, or executing operations. It has minimal blast radius—misuse would only expose already-public or user-accessible profile data. Classified as Read with low severity.
From the tool's definition Tool retrieves profile data ('Get a LinkedIn user profile summary including name, headline, location, about section, experience, and education') with no modification capability. The verb 'get' and description explicitly indicate data retrieval only.
Attacks that exploit this kind of access
Get a LinkedIn user profile summary including name, headline, location, about section, experience, and education. Defaults to the currently logged-in user. It is categorised as a Read tool in the LinkedIn MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LinkedIn MCP Server MCP server in PolicyLayer and add a rule for 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 LinkedIn MCP Server. Nothing to install.
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 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 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.
get_profile is provided by the LinkedIn MCP Server MCP server (markswendsen-code/mcp-linkedin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →