Get aggregated engagement statistics for a LinkedIn account
AI agents call linkedin_account_stats to retrieve information from Publora 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 aggregated engagement statistics from a LinkedIn account. It performs a read-only operation that gathers information without modifying, executing actions, deleting data, or involving financial transactions. The classification as 'Read' is appropriate because the tool's sole function is to obtain statistics data.
From the tool's definition Tool name is 'linkedin_account_stats' and description states it is used to 'Get aggregated engagement statistics for a LinkedIn account'. The verb 'Get' and the nature of retrieving statistics indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Get aggregated engagement statistics for a LinkedIn account. It is categorised as a Read tool in the Publora MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Publora MCP Server MCP server in PolicyLayer and add a rule for linkedin_account_stats: 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 Publora MCP Server. Nothing to install.
linkedin_account_stats 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_account_stats 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_account_stats. 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_account_stats is provided by the Publora MCP Server MCP server (publora/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 →