send_notification

THE RISK

Low Risk

Why send_notification needs a policy

Based on the server context (OS bridge for URLs, clipboard, date info) and the tool name, this likely sends a desktop/OS notification. Sending a notification is a transient, non-destructive side effect that doesn't clearly fall into Read, Write, Execute, Destructive, or Financial categories. It's a notification dispatch with low blast radius. Confidence is low due to empty description.

From the tool's definition Tool name is 'send_notification'; description is empty and uninformative.

Documented attack patterns abuse exactly the kind of access send_notification gives an agent:

POLICY

How to control send_notification

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP System Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for send_notification:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_notification": {
      "limits": [
        {
          "counter": "send_notification_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

send_notification gets a rate cap, and everything else on the server is denied unless you say otherwise.

Create a free account and register MCP System Bridge — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP System Bridge tools

Execute open_urls Open a list of URLs in the default browser. Write copy_to_clipboard Copy text to the clipboard. Read get_current_date_info get_current_date_info

All 4 MCP System Bridge tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about send_notification

What does the send_notification tool do? +

send_notification. It is categorised as a Other tool in the MCP System Bridge MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on send_notification? +

Register the MCP System Bridge MCP server in PolicyLayer and add a rule for send_notification: 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 System Bridge. Nothing to install.

What risk level is send_notification? +

send_notification is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit send_notification? +

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

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

send_notification is provided by the MCP System Bridge MCP server (leynier/mcp-sys-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP System Bridge tool call.

Start from MCP System Bridge, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →