Get recent LinkedIn messages and InMail conversations including sender, preview, and timestamp.
AI agents call get_messages 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 and queries existing message data with no side effects. It is a straightforward read operation that accesses LinkedIn conversation metadata. The low severity reflects minimal blast radius if misused by an AI agent—it only exposes message content the authenticated user already has access to.
From the tool's definition Tool description explicitly states 'Get recent LinkedIn messages' with no modification capabilities—it retrieves sender, preview, and timestamp data only. No create, update, delete, or send operations are performed.
Attacks that exploit this kind of access
Get recent LinkedIn messages and InMail conversations including sender, preview, and timestamp. 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_messages: 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_messages 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_messages 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_messages. 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_messages is provided by the LinkedIn MCP Server MCP server (markswendsen-code/mcp-linkedin). 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 →