login_tenant · MelviChat MCP Server MCP: Risk & Policy

WHAT IT DOES

What login_tenant does on MelviChat MCP Server

AI agents use login_tenant to create or update resources in MelviChat MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MelviChat MCP Server environment.

WHY IT NEEDS A POLICY

Why login_tenant needs a policy

A login operation creates a new session or authentication token, which is a reversible state change (Write). It does not read existing data passively, nor does it execute code or destroy data. Misuse could allow an AI agent to authenticate as a different tenant, potentially gaining unauthorized access to that organization's data and APIs, hence medium severity.

From the tool's definition 'Iniciar sesión como empresa/tenant' — initiates an authenticated session (login) for a tenant/company on the MelviChat platform

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

login_tenant Rate-limited

login_tenant 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "login_tenant": {
      "limits": [
        {
          "counter": "login_tenant_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about login_tenant

What does the login_tenant tool do? +

Iniciar sesión como empresa/tenant. It is categorised as a Write tool in the MelviChat MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on login_tenant? +

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

What risk level is login_tenant? +

login_tenant is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit login_tenant? +

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

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

login_tenant is provided by the MelviChat MCP Server MCP server (melvi24/mcp-chat-ia). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.