AI agents use add_coda to create or update resources in Guitar Pro — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Guitar Pro environment.
The 'add_' prefix combined with the musical context (coda is a section marker in sheet music) indicates this tool creates or modifies data within a Guitar Pro file. This is a Write operation—it changes file content but the change is reversible (can be undone or replaced). It does not delete data (not Destructive), execute arbitrary code (not Execute), or move money (not Financial).
From the tool's definition Tool name 'add_coda' with prefix 'add_' indicates creation/modification of Guitar Pro file content. Description is empty, but sibling tools (add_chord, add_note, add_track, etc.) all modify Guitar Pro files reversibly.
Documented attack patterns abuse exactly the kind of access add_coda gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Guitar Pro, and nothing reaches the server without passing your rules. This is the rule we recommend for add_coda:
{
"version": "1",
"default": "deny",
"tools": {
"add_coda": {
"limits": [
{
"counter": "add_coda_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_coda 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_coda. It is categorised as a Write tool in the Guitar Pro MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Guitar Pro MCP server in PolicyLayer and add a rule for add_coda: 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 Guitar Pro. Nothing to install.
add_coda 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_coda 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_coda. 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_coda is provided by the Guitar Pro MCP server (wegitor/guitar-pro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Guitar Pro, 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.
35 Guitar Pro tools catalogued and risk-classified — across an index of 43,000+ MCP servers.