AI agents use save_guitar_pro 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 tool saves Guitar Pro files, which is a write operation that modifies data on disk. While the description is empty, the context from the server description and sibling tools (add_chord, add_note, add_track, etc.) confirms this performs file persistence. It is Write rather than Destructive because saving typically overwrites/creates reversibly (user can undo or restore from version control), not irreversibly.
From the tool's definition Tool name is 'save_guitar_pro' and server description states it provides tools for 'opening, modifying, and saving Guitar Pro files.' The tool name directly indicates a save operation, which modifies/persists data to a file.
Documented attack patterns abuse exactly the kind of access save_guitar_pro 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 save_guitar_pro:
{
"version": "1",
"default": "deny",
"tools": {
"save_guitar_pro": {
"limits": [
{
"counter": "save_guitar_pro_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_guitar_pro 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.
save_guitar_pro. 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 save_guitar_pro: 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.
save_guitar_pro 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 save_guitar_pro 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 save_guitar_pro. 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.
save_guitar_pro 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.