AI agents call linkedin_get_feed 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 retrieves and queries LinkedIn feed data without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval operation with no destructive, financial, or execution consequences. The low severity reflects minimal blast radius if misused—it would only expose the user's feed visibility.
From the tool's definition Tool name 'linkedin_get_feed' and description 'Get LinkedIn feed/timeline posts' indicate retrieval of data with no modification or side effects.
Attacks that exploit this kind of access
📰 Get LinkedIn feed/timeline posts. 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_get_feed: 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_get_feed 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_feed 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_feed. 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_feed 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 →