// SCAN REPORT

Skippr Extension MCP Server

11 tools. 5 can modify or destroy data without limits.

5 write tools that can modify data. Rate limits recommended.

Last updated: 4 Jul 2026

5 can modify or destroy data

6 read-only

11 tools total

Community server · catalogue entry verified 04/07/2026

How to control Skippr Extension MCP Server ↓

TOOL MAP

What Skippr Extension MCP Server exposes to your agents

Read (6) Write / Execute (5) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Skippr Extension MCP Server tools

Execute · Medium skippr_restart_extension_server Restarting a WebSocket server is an Execute action—it runs an operational command with side effects that depend on the system state. Execute · Medium skippr_send_to_extension This tool triggers an external operation by sending a message to a running browser extension. Execute · Medium skippr_notify_all_extensions Broadcasting a message to all connected extensions triggers an external operation across multiple clients simultaneously. Execute · Medium skippr_verify_issue_fix This tool triggers an active verification process in an external browser extension, constituting an Execute-category action.

5 of Skippr Extension MCP Server's 11 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Skippr Extension MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Skippr Extension MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "skippr_disconnect_extension": {
    "limits": [
      {
        "counter": "skippr_disconnect_extension_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "skippr_extension_server_status": {
    "limits": [
      {
        "counter": "skippr_extension_server_status_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Skippr Extension MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SKIPPR EXTENSION →

Instant setup, no code required.

FULL CATALOGUE

All 11 Skippr Extension MCP Server tools

EXECUTE 4 tools

Execute skippr_notify_all_extensions Broadcasts a message to all connected browser extensions Execute skippr_restart_extension_server Restarts the WebSocket server that communicates with browser extensions Execute skippr_send_to_extension Sends a message to a specific browser extension by its ID Execute skippr_verify_issue_fix Requests verification from the browser extension to check if an issue has been fixed

WRITE 1 tools

Write skippr_disconnect_extension Disconnects a specific browser extension by its ID

READ 6 tools

Read skippr_extension_server_status Gets the current status of the WebSocket server for browser extensions Read skippr_get_issue Gets full details for a specific Skippr issue including raw markdown content Read skippr_list_connected_extensions Lists all currently connected browser extensions Read skippr_list_issues Lists all available Skippr issues with optional filtering by project, review, severity, category, and resoluti Read skippr_list_projects Lists all available project IDs from the .skippr/projects directory Read skippr_notify_project_extensions Sends a message to all browser extensions connected to a specific project

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Skippr Extension MCP Server

How do I prevent bulk modifications through Skippr Extension MCP Server? +

The Skippr Extension MCP Server server has 1 write tools including skippr_disconnect_extension. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Skippr Extension MCP Server.

How many tools does the Skippr Extension MCP Server MCP server expose? +

11 tools across 3 categories: Execute, Read, Write. 6 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on Skippr Extension MCP Server? +

Register the Skippr Extension MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Skippr Extension MCP Server tool call.

Deterministic rules across all 11 Skippr Extension MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SKIPPR EXTENSION →

Instant setup, no code required.

11 Skippr Extension MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.