Get a specific person's LinkedIn profile.
AI agents call get_person_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 retrieves public or accessible LinkedIn profile information about a person. It performs a query/fetch operation without creating, modifying, deleting, or executing any actions. The severity is low because LinkedIn profiles are typically semi-public data, and retrieval alone poses minimal risk unless the data is misused downstream (which is not the tool's direct responsibility).
From the tool's definition Tool name 'get_person_profile' and description 'Get a specific person's LinkedIn profile' indicate data retrieval with no modification or side effects. The verb 'Get' is a classic read operation.
Attacks that exploit this kind of access
Get a specific person's LinkedIn profile. 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_person_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_person_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_person_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_person_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_person_profile is provided by the LinkedIn MCP Server MCP server (selvin-paul-raj/linkedin-mcp-server). 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 →