search_companies
AI agents call search_companies to retrieve information from LinkedIn MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a search/query operation to retrieve company data from LinkedIn. This is a Read operation as it retrieves information without modifying, deleting, or executing external operations. Severity is medium rather than low because LinkedIn's terms of service restrict scraping, and this tool could facilitate unauthorized data collection at scale or privacy violations.
From the tool's definition Tool name 'search_companies' combined with server description indicating data retrieval via 'scraping profiles, companies, job postings' and 'authenticated browser automation.' The tool appears designed to query and retrieve company information from LinkedIn.
Attacks that exploit this kind of access
search_companies. It is categorised as a Read tool in the LinkedIn MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LinkedIn MCP Server MCP server in PolicyLayer and add a rule for search_companies: 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 MCP Server. Nothing to install.
search_companies 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 search_companies 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 search_companies. 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.
search_companies is provided by the LinkedIn MCP Server MCP server (stickerdaniel/linkedin-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.