Low Risk

get_track_notes

get_track_notes

How to control get_track_notes ↓

What get_track_notes does on Guitar Pro

AI agents call get_track_notes to retrieve information from Guitar Pro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_track_notes needs a policy

The tool name strongly suggests it retrieves or queries note information from a Guitar Pro track. No side effects are mentioned or implied. The empty description lowers confidence slightly, but the clear 'get_' prefix and context of a file manipulation server where other tools are explicitly write/add operations supports the Read categorization. This is a low-severity operation as it only accesses existing data.

From the tool's definition Tool name 'get_track_notes' indicates retrieval of note data from a track without modification. The verb 'get' is a standard read operation. No description provided, but the naming pattern is consistent with query/retrieval operations.

Documented attack patterns abuse exactly the kind of access get_track_notes gives an agent:

How to control get_track_notes

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 get_track_notes:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_track_notes": {}
  }
}

get_track_notes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Guitar Pro — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_track_notes

What does the get_track_notes tool do? +

get_track_notes. It is categorised as a Read tool in the Guitar Pro MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_track_notes? +

Register the Guitar Pro MCP server in PolicyLayer and add a rule for get_track_notes: 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.

What risk level is get_track_notes? +

get_track_notes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_track_notes? +

Yes. Add a rate_limit block to the get_track_notes 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.

How do I block get_track_notes completely? +

Set action: deny in the PolicyLayer policy for get_track_notes. 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.

What MCP server provides get_track_notes? +

get_track_notes 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.

Enforce policy on every Guitar Pro tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.