start-notification-stream · Business Central MCP Server MCP

WHAT IT DOES

What start-notification-stream does on Business Central MCP Server

AI agents invoke start-notification-stream to trigger actions in Business Central 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 start-notification-stream needs a policy

This tool initiates an active operation (streaming notifications) rather than passively reading data. While not destructive or financial, it executes a process whose effects depend on arguments ('configurable count'). The 'configurable count' parameter could be abused to spam recipients or exhaust system resources, creating a medium-severity blast radius.

From the tool's definition Tool name 'start-notification-stream' and description 'Sends a stream of notifications with configurable count' indicate the tool triggers an external operation (notification dispatch) with configurable parameters that affect behavior and scope.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start-notification-stream Rate-limited

start-notification-stream 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": {
    "start-notification-stream": {
      "limits": [
        {
          "counter": "start-notification-stream_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 Business Central MCP Server, so you can run agents against it safely.

FAQ

Questions about start-notification-stream

What does the start-notification-stream tool do? +

Sends a stream of notifications with configurable count. It is categorised as a Execute tool in the Business Central 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 start-notification-stream? +

Register the Business Central MCP Server MCP server in PolicyLayer and add a rule for start-notification-stream: 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 Business Central MCP Server. Nothing to install.

What risk level is start-notification-stream? +

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

Can I rate-limit start-notification-stream? +

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

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

start-notification-stream is provided by the Business Central MCP Server MCP server (javiarmesto/lab3_1_mcp_businesscentral). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.