AI agents call get_student_profile 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 student profile information from Handshake, which is a read operation with no stated side effects. Severity is medium rather than low because student profiles may contain sensitive personal/educational data (name, contact, academic record, job preferences) that could be misused if an AI agent queries profiles without proper authorization or context.
From the tool's definition Tool name 'get_student_profile' combined with server description stating it 'pull[s] student or employer profiles' indicates data retrieval.
Attacks that exploit this kind of access
get_student_profile. 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_student_profile: 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_student_profile 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_student_profile 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_student_profile. 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_student_profile 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 →