linkedin_list_reactions
List all reactions (likes, celebrates, etc.) on a specific LinkedIn post.
This record as markdown: /tools/io-github-saloprj-dialogbrain/linkedin-list-reactions.md
What linkedin_list_reactions does on Dialogbrain
AI agents call linkedin_list_reactions to retrieve information from Dialogbrain without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Maximum reactions to return |
post_id | string | Yes | LinkedIn post/activity ID |
Parameters from the server's own tool schema.
Why linkedin_list_reactions is rated Low
This tool retrieves and displays reaction metadata from a LinkedIn post. It performs no data modification, deletion, code execution, or financial operations. The action is read-only and non-destructive, making it a Read category tool with low severity since the data accessed (public reaction counts) poses minimal risk if accessed by an AI agent.
From the tool's definition Tool name 'linkedin_list_reactions' and description 'List all reactions (likes, celebrates, etc.) on a specific LinkedIn post' indicate a retrieval operation that queries existing data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs linkedin_list_reactions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linkedin_list_reactions, this is the rule to start with:
linkedin_list_reactions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every linkedin_list_reactions call is checked against it from then on.
Questions about linkedin_list_reactions
List all reactions (likes, celebrates, etc.) on a specific LinkedIn post. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
linkedin_list_reactions accepts 2 parameters: limit, post_id. Required: post_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for linkedin_list_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 Dialogbrain. Nothing to install.
linkedin_list_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 linkedin_list_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 linkedin_list_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.
linkedin_list_reactions is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue