get_my_profile
AI agents call get_my_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 personal profile information without modification. While it is a Read operation (no side effects), the severity is high because it accesses sensitive personal data (name, contact info, employment history, connections) from an authenticated LinkedIn account.
From the tool's definition Tool name 'get_my_profile' and server context indicating it retrieves authenticated user profile data via LinkedIn; described as 'scraping profiles' in server description.
Attacks that exploit this kind of access
get_my_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_my_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_my_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_my_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_my_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_my_profile is provided by the LinkedIn MCP Server MCP server (stickerdaniel/linkedin-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.