Add a chord symbol in the live score.
AI agents use add_live_chord_symbol 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 creates or adds a new element (chord symbol) to a musical score, which is a reversible modification. It does not execute arbitrary code, delete data irreversibly, move money, or merely read data. The 'medium' severity reflects that misuse could corrupt a musical score, but the damage is localized to notation and easily undone through standard undo/deletion operations.
From the tool's definition Tool name 'add_live_chord_symbol' with description 'Add a chord symbol in the live score' indicates creation of a new musical notation element.
Documented attack patterns abuse exactly the kind of access add_live_chord_symbol 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 add_live_chord_symbol:
{
"version": "1",
"default": "deny",
"tools": {
"add_live_chord_symbol": {
"limits": [
{
"counter": "add_live_chord_symbol_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_live_chord_symbol 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.
Add a chord symbol 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 add_live_chord_symbol: 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.
add_live_chord_symbol 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 add_live_chord_symbol 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 add_live_chord_symbol. 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.
add_live_chord_symbol 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.