Get reactions from a LinkedIn profile. Returns cleaned data in TOON format.
AI agents call get_profile_reactions 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 reaction data from LinkedIn profiles. It performs a read-only operation with no side effects—it neither modifies data, executes commands, deletes records, nor involves financial transactions. The verb 'Get' and the absence of any modification language clearly place this in the Read category.
From the tool's definition Tool name 'get_profile_reactions' and description 'Get reactions from a LinkedIn profile. Returns cleaned data' indicate a retrieval operation with no modification, creation, deletion, or execution of code.
Attacks that exploit this kind of access
Get reactions from a LinkedIn profile. Returns cleaned data in TOON format. 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_profile_reactions: 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_profile_reactions 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_profile_reactions 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_profile_reactions. 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_profile_reactions is provided by the LinkedIn MCP Server MCP server (jing-yilin/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 →