Fetch a specific member's profile by their URN (e.g., 'urn:li:person:123').
AI agents call linkedin_get_member_profile to retrieve information from LinkedIn Custom 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 publicly or permissioned profile information from LinkedIn without creating, modifying, or deleting any data. It is a straightforward query operation that poses minimal security risk if misused by an AI agent, as it only exposes already-accessible professional information. The worst-case scenario would be unauthorized enumeration of profiles, which is a read-level concern.
From the tool's definition Tool name contains 'get' and description explicitly states 'Fetch a specific member's profile'. The operation retrieves profile data with no modification, deletion, or side effects.
Documented attack patterns abuse exactly the kind of access linkedin_get_member_profile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn Custom MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for linkedin_get_member_profile:
{
"version": "1",
"default": "deny",
"tools": {
"linkedin_get_member_profile": {}
}
}linkedin_get_member_profile is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch a specific member's profile by their URN (e.g., 'urn:li:person:123'). It is categorised as a Read tool in the LinkedIn Custom MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LinkedIn Custom MCP Server MCP server in PolicyLayer and add a rule for linkedin_get_member_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 Custom MCP Server. Nothing to install.
linkedin_get_member_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_member_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_member_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_member_profile is provided by the LinkedIn Custom MCP Server MCP server (saramali15792/linkedin_mcp_custom_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LinkedIn Custom MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 LinkedIn Custom MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.