kanka_oauth_login · Kanka MCP: Risk & Policy

WHAT IT DOES

What kanka_oauth_login does on Kanka

AI agents invoke kanka_oauth_login to trigger actions in Kanka. 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 kanka_oauth_login needs a policy

This tool executes a browser-based OAuth flow and persists authentication tokens to disk. It triggers external operations (opening a browser, making network requests to Kanka's authorization server) and writes credential tokens to persistent storage. The blast radius is high because misuse could result in unauthorized access to a user's Kanka account or token theft via token persistence manipulation.

From the tool's definition Run the OAuth 2.0 Authorization Code flow with PKCE. Opens a browser to the Kanka authorize page; on approval, persists access + refresh tokens to disk

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kanka_oauth_login Rate-limited

kanka_oauth_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": {
    "kanka_oauth_login": {
      "limits": [
        {
          "counter": "kanka_oauth_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 Kanka, so you can run agents against it safely.

FAQ

Questions about kanka_oauth_login

What does the kanka_oauth_login tool do? +

Run the OAuth 2.0 Authorization Code flow with PKCE. Opens a browser to the Kanka authorize page; on approval, persists access + refresh tokens to disk so subsequent tool calls authenticate transparently. Requires an OAuth app registered at https://app.kanka.io/settings/api?clients=1. Provide client_id/client_secret here or via KANKA_OAUTH_CLIENT_ID / KANKA_OAUTH_CLIENT_SECRET env vars. It is categorised as a Execute tool in the Kanka MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on kanka_oauth_login? +

Register the Kanka MCP server in PolicyLayer and add a rule for kanka_oauth_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 Kanka. Nothing to install.

What risk level is kanka_oauth_login? +

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

Can I rate-limit kanka_oauth_login? +

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

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

kanka_oauth_login is provided by the Kanka MCP server (torinvdb/kanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.