AI agents call linkedin_request_profile_api_access to retrieve information from Linkedin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool generates text (application text) for a request — it produces content/output but does not submit anything, make API calls, or modify any data. It is essentially a text generation/read operation with no side effects. Severity is low since misuse would only produce some draft text.
From the tool's definition "Generate application text for requesting LinkedIn Profile API access"
Attacks that exploit this kind of access
Generate application text for requesting LinkedIn Profile API access. It is categorised as a Read tool in the Linkedin MCP Server, which means it retrieves data without modifying state.
Register the Linkedin MCP server in PolicyLayer and add a rule for linkedin_request_profile_api_access: 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. Nothing to install.
linkedin_request_profile_api_access 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_request_profile_api_access 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_request_profile_api_access. 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_request_profile_api_access is provided by the Linkedin MCP server (maheidem/linkedin-optimizer-mcp). 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 →