login_user · Stevia Store MCP Server MCP: Risk & Policy

WHAT IT DOES

What login_user does on Stevia Store MCP Server

AI agents invoke login_user to trigger actions in Stevia Store 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_user needs a policy

Logging in creates a session/authentication state, which is an external operation with side effects (session creation, token issuance). It is not a pure read (it mutates auth state) nor a write of user data, nor destructive or financial. Execute is the most appropriate category as it triggers an authentication flow whose effects depend on the provided credentials.

From the tool's definition login_user — triggers an authentication/session operation; description is minimal ('התחברות למערכת' = 'Login to system')

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

login_user Rate-limited

login_user 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_user": {
      "limits": [
        {
          "counter": "login_user_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 Stevia Store MCP Server, so you can run agents against it safely.

FAQ

Questions about login_user

What does the login_user tool do? +

🔑 התחברות למערכת. It is categorised as a Execute tool in the Stevia Store 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_user? +

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

What risk level is login_user? +

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

Can I rate-limit login_user? +

Yes. Add a rate_limit block to the login_user 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_user completely? +

Set action: deny in the PolicyLayer policy for login_user. 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_user? +

login_user is provided by the Stevia Store MCP Server MCP server (yairbarak22/mcpserverstevia). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.