AI agents call get_job_details to retrieve information from Handshake without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to fetch and return job details from the Handshake platform. No modification, deletion, execution, or financial transaction is implied. This is a straightforward data retrieval operation consistent with the read-only nature of the Handshake integration described in the server overview.
From the tool's definition Tool name 'get_job_details' combined with server description stating it enables 'search jobs, browse employers, explore events, and pull student or employer profiles' indicates retrieval of job information.
Attacks that exploit this kind of access
get_job_details. It is categorised as a Read tool in the Handshake MCP Server, which means it retrieves data without modifying state.
Register the Handshake 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 Handshake. 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 Handshake MCP server (sudhxnva/handshake-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 →