AI agents use transpose_track 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.
Transposing a track changes pitch values of notes within a Guitar Pro file, which is a modification (Write category) rather than a destructive delete or an Execute-level code execution. The absence of a description lowers confidence slightly, but the function name and server context (file manipulation) strongly suggest this modifies note data reversibly.
From the tool's definition Tool named 'transpose_track' with no description; sibling tools on this MCP server include 'add_chord', 'add_gp_note', 'add_gp_track', and 'modify'/'save' operations that manipulate Guitar Pro files.
Documented attack patterns abuse exactly the kind of access transpose_track 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 transpose_track:
{
"version": "1",
"default": "deny",
"tools": {
"transpose_track": {
"limits": [
{
"counter": "transpose_track_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}transpose_track 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.
transpose_track. 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 transpose_track: 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.
transpose_track 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 transpose_track 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 transpose_track. 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.
transpose_track 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.