Set a barline type in the live score.
AI agents use set_live_barline 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 score metadata (barline type) in a live editing context but does not delete data or execute arbitrary code. The change is reversible—a barline type can be changed to another value. While it affects a connected music notation application, it remains a targeted structural edit rather than destructive action or code execution.
From the tool's definition Tool description states 'Set a barline type in the live score' — the word 'Set' indicates modification of existing score data. The server integrates with MuseScore, Dorico, and Sibelius for 'live manipulation' of musical notation.
Documented attack patterns abuse exactly the kind of access set_live_barline 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 set_live_barline:
{
"version": "1",
"default": "deny",
"tools": {
"set_live_barline": {
"limits": [
{
"counter": "set_live_barline_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_live_barline 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.
Set a barline type in the live score. 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 set_live_barline: 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.
set_live_barline 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 set_live_barline 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 set_live_barline. 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.
set_live_barline 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.