connect_to_dorico
AI agents call connect_to_dorico as a supporting operation in Mcp Score workflows.
The name suggests establishing a connection to Dorico (a music notation application), which is analogous to sibling tools like connect_to_musescore and connect_to_sibelius. A connection operation is typically low-risk as it doesn't inherently read, write, execute, or destroy data — it sets up a channel for subsequent operations. However, the empty description lowers confidence.
From the tool's definition Tool name is 'connect_to_dorico'; description is empty or uninformative.
Documented attack patterns abuse exactly the kind of access connect_to_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 connect_to_dorico:
{
"version": "1",
"default": "deny",
"tools": {
"connect_to_dorico": {
"limits": [
{
"counter": "connect_to_dorico_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} connect_to_dorico gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
connect_to_dorico. It is categorised as a Other tool in the Mcp Score MCP Server, which means it performs auxiliary operations.
Register the Mcp Score MCP server in PolicyLayer and add a rule for connect_to_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.
connect_to_dorico is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the connect_to_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 connect_to_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.
connect_to_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.