AI agents call get_event_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 retrieves event details from the Handshake platform. Based on the naming pattern and the server's stated purpose to 'search jobs, browse employers, explore events, and pull student or employer profiles,' this is a read-only query operation. The empty description prevents highest confidence, but contextual evidence from sibling tools and the server's read-oriented function is strong.
From the tool's definition Tool name 'get_event_details' and sibling tools 'search_events', 'search_jobs', 'get_job_details', 'get_student_profile', 'get_employer_profile' all operate on a Handshake career platform to retrieve data.
Attacks that exploit this kind of access
get_event_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_event_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_event_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_event_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_event_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_event_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 →