Log in to eClass using username/password from your .env file through UoA
AI agents use login to create or update resources in eClass MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your eClass MCP Server environment.
Login establishes an authenticated session, which is a state-creating (write) operation. It is not purely read-only since it creates a session on the server. It is not destructive or financial. Misuse could allow unauthorized access to course data and platform operations, hence medium severity.
From the tool's definition Log in to eClass using username/password from your .env file through UoA
Documented attack patterns abuse exactly the kind of access login gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and eClass MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for login:
{
"version": "1",
"default": "deny",
"tools": {
"login": {
"limits": [
{
"counter": "login_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}login stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Log in to eClass using username/password from your .env file through UoA. It is categorised as a Write tool in the eClass MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the eClass MCP Server MCP server in PolicyLayer and add a rule for login: 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 eClass MCP Server. Nothing to install.
login is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the login 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 login. 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.
login is provided by the eClass MCP Server MCP server (sdi2200262/eclass-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from eClass MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 eClass MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.