AI agents use export_to_midi 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.
Export operations that generate new files or data formats are Write actions—they create or produce data (the MIDI output) that can be stored and reused. While non-destructive and reversible, the tool creates new persistent data. The empty description limits confidence slightly, but contextual clues from the server's purpose and similar tools support this classification.
From the tool's definition Tool name 'export_to_midi' indicates conversion/transformation of Guitar Pro file data to MIDI format. The server description states it provides tools for 'manipulating Guitar Pro files through a standardized interface.' Sibling tools include…
Documented attack patterns abuse exactly the kind of access export_to_midi 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 export_to_midi:
{
"version": "1",
"default": "deny",
"tools": {
"export_to_midi": {
"limits": [
{
"counter": "export_to_midi_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_to_midi 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.
export_to_midi. 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 export_to_midi: 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.
export_to_midi 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 export_to_midi 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 export_to_midi. 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.
export_to_midi 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.