linkedin_search_companies
AI agents call linkedin_search_companies to retrieve information from WWIDE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries company data from LinkedIn without modifying, deleting, or executing external operations. The naming convention and context of sibling tools confirm this is a search/query operation.
From the tool's definition Tool name 'linkedin_search_companies' indicates a search operation. Sibling tools include 'linkedin_search_people', 'linkedin_get_company', and 'linkedin_get_profile', all of which are read-only query operations.
Attacks that exploit this kind of access
linkedin_search_companies. It is categorised as a Read tool in the WWIDE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WWIDE MCP Server MCP server in PolicyLayer and add a rule for linkedin_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 WWIDE MCP Server. Nothing to install.
linkedin_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 linkedin_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 linkedin_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.
linkedin_search_companies is provided by the WWIDE MCP Server MCP server (kulvir88/salesforce-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 →