AI agents call get_profile_interests to retrieve information from LinkedIn Intelligence 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 interest data from LinkedIn profiles, a query operation with no side effects. While the empty description reduces confidence slightly, the context of the server (profile research, data retrieval) and the naming pattern (get_*) strongly suggest a non-destructive read operation. No evidence of creating, modifying, deleting, executing code, or financial operations.
From the tool's definition Tool name 'get_profile_interests' indicates data retrieval. The empty description limits specificity, but the naming convention aligns with other Read-category sibling tools like 'batch_get_profiles' and 'analyze_*' tools that query LinkedIn data without…
Documented attack patterns abuse exactly the kind of access get_profile_interests gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn Intelligence MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_profile_interests:
{
"version": "1",
"default": "deny",
"tools": {
"get_profile_interests": {}
}
}get_profile_interests is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_profile_interests. It is categorised as a Read tool in the LinkedIn Intelligence MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LinkedIn Intelligence MCP Server MCP server in PolicyLayer and add a rule for get_profile_interests: 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 Intelligence MCP Server. Nothing to install.
get_profile_interests 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_profile_interests 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_profile_interests. 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_profile_interests is provided by the LinkedIn Intelligence MCP Server MCP server (southleft/linkedin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 87 LinkedIn Intelligence MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
87 LinkedIn Intelligence MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.