teamsnap_auth · TeamSnap MCP Server MCP: Risk & Policy

WHAT IT DOES

What teamsnap_auth does on TeamSnap MCP Server

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

This tool triggers an external operation (opening a browser window and initiating an OAuth authentication flow) rather than simply reading or writing data. It causes side effects in the environment by launching a browser and interacting with an external OAuth provider. Severity is medium because misuse could result in unauthorized credential usage or session hijacking, though it requires user interaction to complete.

From the tool's definition Opens a browser window for OAuth login

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

teamsnap_auth Rate-limited

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

FAQ

Questions about teamsnap_auth

What does the teamsnap_auth tool do? +

Authenticate with TeamSnap. Opens a browser window for OAuth login. Credentials are loaded from environment variables (TEAMSNAP_CLIENT_ID, TEAMSNAP_CLIENT_SECRET) or can be passed as arguments. It is categorised as a Execute tool in the TeamSnap 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 teamsnap_auth? +

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

What risk level is teamsnap_auth? +

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

Can I rate-limit teamsnap_auth? +

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

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

teamsnap_auth is provided by the TeamSnap MCP Server MCP server (mrelph/teamsnapmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.