get_job_details
AI agents call get_job_details to retrieve information from MCP-LinkedIn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the naming convention and context from sibling tools which are all Read operations, this tool most likely retrieves job details from LinkedIn without modifying data. The 'get_' prefix is consistent with read-only queries. Confidence is moderate (0.75) rather than high due to the empty description, which prevents direct verification of actual functionality.
From the tool's definition Tool name 'get_job_details' suggests retrieval of job information. Description is empty, but naming pattern matches sibling Read tools (get_company_profile, get_person_profile, get_recommended_jobs, search_jobs) on the same MCP-LinkedIn server.
Attacks that exploit this kind of access
get_job_details. It is categorised as a Read tool in the MCP-LinkedIn MCP Server, which means it retrieves data without modifying state.
Register the MCP-LinkedIn MCP server in PolicyLayer and add a rule for get_job_details: 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 MCP-LinkedIn. Nothing to install.
get_job_details 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_job_details 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_job_details. 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_job_details is provided by the MCP-LinkedIn MCP server (logos-parthenos-ai/linkedin-mcp-server). 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 →