tidal_login · TIDAL MCP: My Custom Picks MCP: Risk & Policy

WHAT IT DOES

What tidal_login does on TIDAL MCP: My Custom Picks

AI agents invoke tidal_login to trigger actions in TIDAL MCP: My Custom Picks. 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 tidal_login needs a policy

This tool triggers an external browser-based authentication flow, which constitutes an external operation/side effect beyond simple data retrieval. It initiates an OAuth or similar login process in the user's browser, which can have session and credential implications. It is not purely a Read operation since it actively opens a browser and establishes an authenticated session.

From the tool's definition Authenticate with TIDAL through browser login flow

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tidal_login Rate-limited

tidal_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": {
    "tidal_login": {
      "limits": [
        {
          "counter": "tidal_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: My Custom Picks, so you can run agents against it safely.

FAQ

Questions about tidal_login

What does the tidal_login tool do? +

Authenticate with TIDAL through browser login flow. It is categorised as a Execute tool in the TIDAL MCP: My Custom Picks MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tidal_login? +

Register the TIDAL MCP: My Custom Picks MCP server in PolicyLayer and add a rule for tidal_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: My Custom Picks. Nothing to install.

What risk level is tidal_login? +

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

Can I rate-limit tidal_login? +

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

Set action: deny in the PolicyLayer policy for tidal_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 tidal_login? +

tidal_login is provided by the TIDAL MCP: My Custom Picks MCP server (mikeysrecipes/tidal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.