AI agents call get_student_history to retrieve information from Leafeep without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical data about a student. It performs a read-only query with no side effects, no data modification, and no irreversible actions. The blast radius of misuse is limited to unauthorized access to student records, which is a low-severity concern (data confidentiality issue rather than integrity or availability).
From the tool's definition Tool name is 'get_student_history' and description states 'Get a student' — a retrieval operation with no modification or deletion. In the context of an educational quiz/grading server, this queries student data (history, performance records).
Attacks that exploit this kind of access
Get a student. It is categorised as a Read tool in the Leafeep MCP Server, which means it retrieves data without modifying state.
Register the Leafeep MCP server in PolicyLayer and add a rule for get_student_history: 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 Leafeep. Nothing to install.
get_student_history 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_history 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_history. 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_history is provided by the Leafeep MCP server (xhae123/leafeep-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 →