AI agents call list_students 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 and queries student data (names and scores) without creating, modifying, deleting, or executing any operations. It is a straightforward read operation typical of an educational management system.
From the tool's definition Tool name 'list_students' and description 'List all students with scores' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
List all students with scores. 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 list_students: 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.
list_students 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 list_students 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 list_students. 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.
list_students 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 →