linkedin_get_profile
AI agents call linkedin_get_profile 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.
The tool name clearly indicates a GET operation (read/retrieval). Despite the empty description, the naming convention and context from sibling tools strongly suggest this retrieves LinkedIn profile information. Profile retrieval is a read-only operation with no side effects, alignment, or data modification.
From the tool's definition Tool name 'linkedin_get_profile' indicates a retrieval operation. Sibling tools on the server include 'linkedin_get_company', 'linkedin_get_company_posts', and 'linkedin_search_people', which are all Read operations.
Attacks that exploit this kind of access
linkedin_get_profile. 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_get_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 WWIDE MCP Server. Nothing to install.
linkedin_get_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 linkedin_get_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 linkedin_get_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.
linkedin_get_profile 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 →