Get the authenticated LinkedIn user\
AI agents call linkedin_get_my_email 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 user profile information (email address) from LinkedIn after authentication. It is purely a read operation that queries data without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an agent could learn a user's email, but this is relatively low-impact information exposure.
From the tool's definition Tool name 'linkedin_get_my_email' and description 'Get the authenticated LinkedIn user' indicate retrieval of user email data with no modification or side effects.
Attacks that exploit this kind of access
Get the authenticated LinkedIn 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 linkedin_get_my_email: 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.
linkedin_get_my_email 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_my_email 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_my_email. 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_my_email is provided by the LinkedIn MCP Server MCP server (souravdasbiswas/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 →