login · TIDAL MCP Server MCP: Risk & Policy

Q: What risk level is login?

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

WHAT IT DOES

What login does on TIDAL MCP Server

AI agents invoke login to trigger actions in TIDAL 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 needs a policy

The login tool triggers an external OAuth browser flow — an external operation that opens a browser, redirects through authentication pages, and establishes a session/token. This is an active execution of an external process rather than a simple read or write. Misuse could result in credential theft, session hijacking, or unauthorized account access, making it high severity.

From the tool's definition Authenticate with TIDAL using OAuth browser flow

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

login 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": {
      "limits": [
        {
          "counter": "login_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 TIDAL MCP Server, so you can run agents against it safely.

FAQ

Questions about login

What does the login tool do? +

Authenticate with TIDAL using OAuth browser flow. It is categorised as a Execute tool in the TIDAL 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? +

Register the TIDAL 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 TIDAL 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 TIDAL MCP Server MCP server (keenanbb/tidal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.