Report whether a persistent LinkedIn profile is present.
AI agents call session_status to retrieve information from Linkedin Company Admin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the current session state to determine if a LinkedIn profile session exists. It is a simple information-retrieval operation with no side effects, no data modification, no code execution, and no destructive capability. It falls squarely into the Read category with low severity since misuse would only expose whether a session is active, not sensitive data or operational capability.
From the tool's definition Tool name 'session_status' and description 'Report whether a persistent LinkedIn profile is present' indicate a status check that retrieves session state information without modifying anything.
Attacks that exploit this kind of access
Report whether a persistent LinkedIn profile is present. It is categorised as a Read tool in the Linkedin Company Admin MCP Server, which means it retrieves data without modifying state.
Register the Linkedin Company Admin MCP server in PolicyLayer and add a rule for session_status: 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 Company Admin. Nothing to install.
session_status 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 session_status 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 session_status. 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.
session_status is provided by the Linkedin Company Admin MCP server (negrueu/linkedin-company-admin-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 →