get_company_profile
AI agents call get_company_profile to retrieve information from MCP-LinkedIn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve company profile information from LinkedIn, consistent with other 'get_*' tools on the server that query data without modification. Read operations have inherently low severity since they do not alter data or trigger financial/destructive actions. Lower confidence (0.7) applied due to absent description, but the naming pattern and server context suggest a safe data retrieval function.
From the tool's definition Tool name 'get_company_profile' indicates data retrieval. Description is empty, limiting certainty. Based on naming convention consistent with sibling tools (get_job_details, get_person_profile) which are Read operations.
Attacks that exploit this kind of access
get_company_profile. It is categorised as a Read tool in the MCP-LinkedIn MCP Server, which means it retrieves data without modifying state.
Register the MCP-LinkedIn MCP server in PolicyLayer and add a rule for get_company_profile: 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 MCP-LinkedIn. Nothing to install.
get_company_profile 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 get_company_profile 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 get_company_profile. 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.
get_company_profile is provided by the MCP-LinkedIn MCP server (logos-parthenos-ai/linkedin-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 →