login_to_lms · LMS MCP Server MCP: Risk & Policy

WHAT IT DOES

What login_to_lms does on LMS MCP Server

AI agents invoke login_to_lms to trigger actions in LMS MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why login_to_lms needs a policy

This tool initiates an authenticated session on an external system (the university LMS), involving CAPTCHA solving and session management. It triggers external operations with side effects (creating an authenticated session), placing it in the Execute category. Severity is high because misuse could expose a student's full academic account to unauthorized access.

From the tool's definition Login to the university LMS system with credentials

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

login_to_lms Rate-limited

login_to_lms stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "login_to_lms": {
      "limits": [
        {
          "counter": "login_to_lms_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LMS MCP Server, so you can run agents against it safely.

FAQ

Questions about login_to_lms

What does the login_to_lms tool do? +

Login to the university LMS system with credentials. It is categorised as a Execute tool in the LMS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on login_to_lms? +

Register the LMS MCP Server MCP server in PolicyLayer and add a rule for login_to_lms: 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 LMS MCP Server. Nothing to install.

What risk level is login_to_lms? +

login_to_lms is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit login_to_lms? +

Yes. Add a rate_limit block to the login_to_lms 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.

How do I block login_to_lms completely? +

Set action: deny in the PolicyLayer policy for login_to_lms. 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.

What MCP server provides login_to_lms? +

login_to_lms is provided by the LMS MCP Server MCP server (qaziabsaar/lms_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.