List followers of the company page.
AI agents call company_list_followers 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.
This tool retrieves follower information from a LinkedIn company page. It is purely a read operation that queries existing data without creating, modifying, deleting, or executing any actions. The blast radius is minimal—exposing a list of followers is a standard, publicly-oriented metric on company pages with no destructive consequences.
From the tool's definition Tool name 'company_list_followers' and description 'List followers of the company page' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
List followers of the company page. 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 company_list_followers: 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.
company_list_followers 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 company_list_followers 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 company_list_followers. 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.
company_list_followers 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 →