skippr_notify_all_extensions

WHAT IT DOES

What skippr_notify_all_extensions does on Skippr Extension MCP Server

AI agents invoke skippr_notify_all_extensions 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_notify_all_extensions needs a policy

Broadcasting a message to all connected extensions triggers an external operation across multiple clients simultaneously. This is not a simple read or write — it executes an action (sending a broadcast) that causes side effects in all connected browser extensions. The blast radius is medium because a misconfigured or malicious message could affect all connected extension instances at once.

From the tool's definition Broadcasts a message to all connected browser extensions

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

skippr_notify_all_extensions Rate-limited

skippr_notify_all_extensions 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_notify_all_extensions": {
      "limits": [
        {
          "counter": "skippr_notify_all_extensions_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_notify_all_extensions

What does the skippr_notify_all_extensions tool do? +

Broadcasts a message to all connected 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_notify_all_extensions? +

Register the Skippr Extension MCP Server MCP server in PolicyLayer and add a rule for skippr_notify_all_extensions: 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_notify_all_extensions? +

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

Can I rate-limit skippr_notify_all_extensions? +

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

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

skippr_notify_all_extensions 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.