Disconnect from Dorico.
AI agents use disconnect_from_dorico to create or update resources in Mcp Score — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Score environment.
This tool modifies an active connection state by disconnecting from the Dorico music notation application. While it changes system state (the connection is terminated), this is a reversible operation—the connection can be re-established using the complementary 'connect_to_dorico' tool shown among siblings. It does not delete data, execute arbitrary code, or trigger irreversible actions.
From the tool's definition Tool name 'disconnect_from_dorico' and description 'Disconnect from Dorico' indicate a connection state modification rather than a destructive or execute operation.
Documented attack patterns abuse exactly the kind of access disconnect_from_dorico gives an agent:
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_dorico:
{
"version": "1",
"default": "deny",
"tools": {
"disconnect_from_dorico": {
"limits": [
{
"counter": "disconnect_from_dorico_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}disconnect_from_dorico stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Disconnect from Dorico. It is categorised as a Write tool in the Mcp Score MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Score MCP server in PolicyLayer and add a rule for disconnect_from_dorico: 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.
disconnect_from_dorico is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the disconnect_from_dorico 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.
Set action: deny in the PolicyLayer policy for disconnect_from_dorico. 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.
disconnect_from_dorico 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.
Start from Mcp Score, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Mcp Score tools catalogued and risk-classified — across an index of 43,000+ MCP servers.