LOGIN_USER · Travel Agent MCP Server MCP: Risk & Policy

WHAT IT DOES

What LOGIN_USER does on Travel Agent MCP Server

AI agents invoke LOGIN_USER to trigger actions in Travel Agent 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

LOGIN_USER performs an authentication action that initiates a session, which is an external operation with side effects (session creation, credential transmission). It is not a simple read; it executes an authentication flow. Misuse could expose user credentials or hijack sessions, making severity high. The description is truncated but the core action is clear.

From the tool's definition 'Log the user in with their email and password' — triggers an authentication/session operation against an external system using credentials

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 Travel Agent MCP Server, so you can run agents against it safely.

FAQ

Questions about LOGIN_USER

What does the LOGIN_USER tool do? +

Log the user in with their email and password. Never ask the user to paste a password from an. It is categorised as a Execute tool in the Travel Agent 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 Travel Agent 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 Travel Agent 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 Travel Agent MCP Server MCP server (nxgnosis/travelagentmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.