Get combined LinkedIn profile overview: followers + post statistics
AI agents call linkedin_profile_summary 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 aggregated profile data (followers and post statistics) from LinkedIn without creating, modifying, or deleting any data. It has no side effects and poses minimal risk if misused—an agent could only gain visibility into publicly available profile metrics. Classified as Read with low severity.
From the tool's definition Tool name 'linkedin_profile_summary' and description 'Get combined LinkedIn profile overview' indicate data retrieval.
Attacks that exploit this kind of access
Get combined LinkedIn profile overview: followers + post statistics. 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_profile_summary: 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_profile_summary 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_profile_summary 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_profile_summary. 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_profile_summary 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 →