skippr_send_to_extension · Skippr Extension MCP Server MCP

WHAT IT DOES

What skippr_send_to_extension does on Skippr Extension MCP Server

AI agents invoke skippr_send_to_extension 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_send_to_extension needs a policy

This tool triggers an external operation by sending a message to a running browser extension. The effects depend on the message content and how the extension handles it, making this an Execute-category action. It's not purely Read/Write since it drives external browser-side behavior.

From the tool's definition Sends a message to a specific browser extension by its ID

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

skippr_send_to_extension Rate-limited

skippr_send_to_extension 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_send_to_extension": {
      "limits": [
        {
          "counter": "skippr_send_to_extension_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_send_to_extension

What does the skippr_send_to_extension tool do? +

Sends a message to a specific browser extension by its ID. 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_send_to_extension? +

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

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

Can I rate-limit skippr_send_to_extension? +

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

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

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