personal_read_company_mentions
AI agents call personal_read_company_mentions to retrieve information from Linkedin Company Admin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty tool description, the naming pattern ('read') and context from the server description and sibling tools strongly indicate this tool retrieves mention data without side effects. It aligns with the 'Read' category for data retrieval operations. Confidence is slightly lowered (0.85 rather than 0.95) due to the missing tool description, but the contextual evidence is substantial.
From the tool's definition Tool name 'personal_read_company_mentions' contains 'read', and the server description explicitly states 'Enables reading analytics' as a core function.
Attacks that exploit this kind of access
personal_read_company_mentions. It is categorised as a Read tool in the Linkedin Company Admin MCP Server, which means it retrieves data without modifying state.
Register the Linkedin Company Admin MCP server in PolicyLayer and add a rule for personal_read_company_mentions: 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 Company Admin. Nothing to install.
personal_read_company_mentions 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 personal_read_company_mentions 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 personal_read_company_mentions. 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.
personal_read_company_mentions is provided by the Linkedin Company Admin MCP server (negrueu/linkedin-company-admin-mcp). 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 →