disconnect_from_sibelius

THE RISK

Low Risk

Why disconnect_from_sibelius needs a policy

Disconnecting from an external application is a session/connection management action. It does not read data, write/modify data, execute code, destroy data, or move money. It simply closes a communication channel, placing it in the 'Other' category. Misuse has minimal blast radius beyond losing the active connection.

From the tool's definition 'Disconnect from Sibelius' — terminates a connection to the Sibelius application

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

POLICY

How to control disconnect_from_sibelius

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

policy.json

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

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

Create a free account and register Mcp Score — 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 Score tools

Write add_live_chord_symbol Add a chord symbol in the live score. Write add_live_rehearsal_mark Add a rehearsal mark in the live score. Write disconnect_from_dorico Disconnect from Dorico. Write disconnect_from_musescore Disconnect from MuseScore. Write set_live_barline Set a barline type in the live score. Write set_live_key_signature Set the key signature in the live score. Write set_live_tempo Set the tempo in the live score. Write transpose_passage transpose_passage

All 18 Mcp Score 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 disconnect_from_sibelius

What does the disconnect_from_sibelius tool do? +

Disconnect from Sibelius. It is categorised as a Other tool in the Mcp Score MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on disconnect_from_sibelius? +

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

What risk level is disconnect_from_sibelius? +

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

Can I rate-limit disconnect_from_sibelius? +

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

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

disconnect_from_sibelius is provided by the Mcp Score MCP server (tskovlund/mcp-score). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Score tool call.

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

CHECK YOUR STACK →