kunobi_refresh · Kunobi MCP Server MCP: Risk & Policy

WHAT IT DOES

What kunobi_refresh does on Kunobi MCP Server

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

This tool triggers an active operation — forcing a reconnect to external services — rather than simply reading data. It causes side effects (re-establishing connections, re-discovering tools, refreshing state across all variants), which puts it in the Execute category. However, it does not modify user data, run arbitrary code, or have destructive/financial implications, so severity is low.

From the tool's definition Force an immediate reconnect attempt across all configured Kunobi variants

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kunobi_refresh Rate-limited

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

FAQ

Questions about kunobi_refresh

What does the kunobi_refresh tool do? +

Force an immediate reconnect attempt across all configured Kunobi variants. Use this after launching Kunobi or when kunobi_status shows stale data. Returns the fresh connection status for all variants. It is categorised as a Execute tool in the Kunobi 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 kunobi_refresh? +

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

What risk level is kunobi_refresh? +

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

Can I rate-limit kunobi_refresh? +

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

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

kunobi_refresh is provided by the Kunobi MCP Server MCP server (kunobi-ninja/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.