login

Q: What risk level is login?

login is a Other tool with low risk. Read-only tools are generally safe to allow by default.

THE RISK

Low Risk

Why login needs a policy

This tool performs authentication to obtain a token. It doesn't read application data, write/modify data, execute code, delete anything, or move money. It's an auth handshake that enables subsequent operations. Closest to 'Other' since authentication itself is a supporting action, though token acquisition could be misused for session hijacking — hence medium-low concern.

From the tool's definition Login with Kinde to get authentication token

Documented attack patterns abuse exactly the kind of access login gives an agent:

POLICY

How to control login

PolicyLayer is an MCP gateway — it sits between your AI agents and Todo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for login:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "login": {
      "limits": [
        {
          "counter": "login_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

Create a free account and register Todo MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Todo MCP Server tools

Financial upgrade_subscription Upgrade user subscription to paid plan Destructive delete_todo Delete a todo item with interactive prompts Destructive logout Logout and clear stored authentication token Write create_todo Create a new todo item with interactive prompts Write save_token Save your Kinde authentication token for future use Write update_todo Update an existing todo item with interactive prompts Read get_kinde_billing Get Kinde billing information and subscription status Read get_subscription_status Get the user\

All 11 Todo MCP Server tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about login

What does the login tool do? +

Login with Kinde to get authentication token. It is categorised as a Other tool in the Todo MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on login? +

Register the Todo 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 Todo MCP Server. Nothing to install.

What risk level is login? +

Can I rate-limit login? +

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.

How do I block login completely? +

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.

What MCP server provides login? +

login is provided by the Todo MCP Server MCP server (sholajegede/todo_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Todo MCP Server tool call.

Start from Todo MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →