AI agents call list_enrollments to retrieve information from Systemeio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists existing enrollment information—a standard data retrieval operation with no side effects. It does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal; an agent could at worst view enrollment records it shouldn't access, but cannot change or harm data.
From the tool's definition Tool name 'list_enrollments' and description 'List course enrollments. See which contacts are enrolled in which courses.' indicate a read-only query operation that retrieves enrollment data without modifying or deleting it.
Attacks that exploit this kind of access
List course enrollments. See which contacts are enrolled in which courses. It is categorised as a Read tool in the Systemeio MCP Server, which means it retrieves data without modifying state.
Register the Systemeio MCP server in PolicyLayer and add a rule for list_enrollments: 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 Systemeio. Nothing to install.
list_enrollments 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_enrollments 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_enrollments. 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_enrollments is provided by the Systemeio MCP server (snzeeee/mcp-server-systemeio). 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 →