notify_deck

Show a desktop notification on the Deck.

SERVERMcp Control Plane SOURCEalbertik322-sudo/mcp-control-plane

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-control-plane/notify-deck.md

WHAT IT DOES

What notify_deck does on Mcp Control Plane

AI agents invoke notify_deck to trigger actions in Mcp Control Plane. 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.

RISK

Why notify_deck is rated High

This tool causes a side effect by displaying a notification on a desktop/deck interface. It doesn't read or write data persistently, but it does trigger an external operation on a UI system. Misuse could involve spamming notifications or displaying misleading content, but the blast radius is low since it only affects a visual notification.

From the tool's definition 'Show a desktop notification on the Deck' — triggers an external operation (displaying a notification on a UI surface)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs notify_deck safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For notify_deck, this is the rule to start with:

notify_deck Rate-limited

notify_deck 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": {
    "notify_deck": {
      "limits": [
        {
          "counter": "notify_deck_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every notify_deck call is checked against it from then on.

FAQ

Questions about notify_deck

What does the notify_deck tool do? +

Show a desktop notification on the Deck. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on notify_deck? +

Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for notify_deck: 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 Mcp Control Plane. Nothing to install.

What risk level is notify_deck? +

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

Can I rate-limit notify_deck? +

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

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

notify_deck is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Control Plane, and thousands of servers like it.

This server

All 286 Mcp Control Plane tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →