skippr_restart_extension_server

WHAT IT DOES

What skippr_restart_extension_server does on Skippr Extension MCP Server

AI agents invoke skippr_restart_extension_server to trigger actions in Skippr Extension 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 skippr_restart_extension_server needs a policy

Restarting a WebSocket server is an Execute action—it runs an operational command with side effects that depend on the system state. While not destructive (data is not lost) and not directly harmful to application data, restarting infrastructure services can disrupt ongoing operations, disconnect active clients, and interrupt communication between the extension and its backend.

From the tool's definition Tool 'skippr_restart_extension_server' performs a server restart operation. The description states it 'Restarts the WebSocket server that communicates with browser extensions,' which is an active operational command that triggers external state changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

skippr_restart_extension_server Rate-limited

skippr_restart_extension_server 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": {
    "skippr_restart_extension_server": {
      "limits": [
        {
          "counter": "skippr_restart_extension_server_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 Skippr Extension MCP Server, so you can run agents against it safely.

FAQ

Questions about skippr_restart_extension_server

What does the skippr_restart_extension_server tool do? +

Restarts the WebSocket server that communicates with browser extensions. It is categorised as a Execute tool in the Skippr Extension 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 skippr_restart_extension_server? +

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

What risk level is skippr_restart_extension_server? +

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

Can I rate-limit skippr_restart_extension_server? +

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

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

skippr_restart_extension_server is provided by the Skippr Extension MCP Server MCP server (skippr-hq/extension-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.