connect_sanka · Sanka MCP Server MCP: Risk & Policy

WHAT IT DOES

What connect_sanka does on Sanka MCP Server

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

This tool initiates or resumes an OAuth connection flow with an external service (Sanka). It doesn't merely read data or write records, but rather executes an external authentication/authorization process. The blast radius is medium — misuse could result in unintended OAuth connections or session establishment, but it doesn't directly delete data or move money.

From the tool's definition 'Start or resume the Sanka OAuth connection flow' — triggers an external OAuth authentication flow/operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_sanka Rate-limited

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

FAQ

Questions about connect_sanka

What does the connect_sanka tool do? +

Start or resume the Sanka OAuth connection flow. Use this when the user explicitly asks to connect or reconnect Sanka. It is categorised as a Execute tool in the Sanka 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 connect_sanka? +

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

What risk level is connect_sanka? +

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

Can I rate-limit connect_sanka? +

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

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

connect_sanka is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.