Low Risk

get_company

Get company information from LinkedIn.

How to control get_company ↓

What get_company does on LinkedIn Model Context Protocol (MCP) Server

AI agents call get_company to retrieve information from LinkedIn Model Context Protocol (MCP) Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_company needs a policy

This tool retrieves company information without side effects. It performs a query/fetch operation similar to other Read-category tools on this server (get_profile, get_job_details, list_applications). Company information on LinkedIn is typically public data, and retrieval alone poses minimal risk of misuse compared to tools that modify data or execute actions.

From the tool's definition Tool name 'get_company' and description 'Get company information from LinkedIn' indicate retrieval of publicly available company data with no modification or execution of operations.

Documented attack patterns abuse exactly the kind of access get_company gives an agent:

How to control get_company

PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn Model Context Protocol (MCP) Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_company:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_company": {}
  }
}

get_company is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register LinkedIn Model Context Protocol (MCP) Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_company

What does the get_company tool do? +

Get company information from LinkedIn. It is categorised as a Read tool in the LinkedIn Model Context Protocol (MCP) Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_company? +

Register the LinkedIn Model Context Protocol (MCP) Server MCP server in PolicyLayer and add a rule for get_company: 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 Model Context Protocol (MCP) Server. Nothing to install.

What risk level is get_company? +

get_company is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_company? +

Yes. Add a rate_limit block to the get_company 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.

How do I block get_company completely? +

Set action: deny in the PolicyLayer policy for get_company. 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.

What MCP server provides get_company? +

get_company is provided by the LinkedIn Model Context Protocol (MCP) Server MCP server (rayyan9477/linkedin_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every LinkedIn Model Context Protocol (MCP) Server tool call.

Start from LinkedIn Model Context Protocol (MCP) Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

13 LinkedIn Model Context Protocol (MCP) Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.