get_sidebar_profiles
AI agents call get_sidebar_profiles 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 naming pattern ('get_*') and sibling tools (get_company_profile, get_job_details, get_feed, etc.) all retrieve data without modification. 'Sidebar profiles' likely refers to fetching LinkedIn profile summaries or recommendations shown in the sidebar UI.
From the tool's definition Tool name 'get_sidebar_profiles' suggests data retrieval. Server context indicates 'scraping profiles' and 'authenticated browser automation' for querying LinkedIn data. Tool description is empty, limiting specificity.
Attacks that exploit this kind of access
get_sidebar_profiles. 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 get_sidebar_profiles: 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.
get_sidebar_profiles 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_sidebar_profiles 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_sidebar_profiles. 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_sidebar_profiles 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.