self_update · CIB Seven MCP Server MCP: Risk & Policy

WHAT IT DOES

What self_update does on CIB Seven MCP Server

AI agents invoke self_update to trigger actions in CIB Seven 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 self_update needs a policy

This tool executes a software update process (npm or git operations) that modifies the installed application on the host system and requires a server restart. It is an external operation with significant side effects — replacing executable code on the system — which classifies it as Execute.

From the tool's definition 'Update cib7-mcp to the latest version. Auto-detects npm vs git install. Server must be restarted after.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

self_update Rate-limited

self_update 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": {
    "self_update": {
      "limits": [
        {
          "counter": "self_update_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 CIB Seven MCP Server, so you can run agents against it safely.

FAQ

Questions about self_update

What does the self_update tool do? +

Update cib7-mcp to the latest version. Auto-detects npm vs git install. Server must be restarted after. Always confirm with the user before calling this tool. It is categorised as a Execute tool in the CIB Seven 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 self_update? +

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

What risk level is self_update? +

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

Can I rate-limit self_update? +

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

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

self_update is provided by the CIB Seven MCP Server MCP server (krixerx/cib7-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.