company_read_page
AI agents call company_read_page 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 lowering confidence slightly, the tool name prefix 'read_' and the server's stated capability to read analytics and page information clearly indicate a Read operation with no side effects.
From the tool's definition Tool name 'company_read_page' indicates a read operation on company page data. Server description confirms it 'enables reading analytics, managing posts, editing page details' with reading as a primary function.
Attacks that exploit this kind of access
company_read_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_read_page: 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_read_page 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_read_page 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_read_page. 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_read_page 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 →