AI agents call get_page_setup 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.
Despite the empty description lowering confidence slightly, the naming convention 'get_*' is a standard indicator of read-only retrieval operations. Page setup configuration is metadata queried from the file, not modified or executed. This falls squarely into the Read category with low severity since it merely retrieves non-sensitive formatting preferences.
From the tool's definition Tool name 'get_page_setup' indicates retrieval of page configuration data from a Guitar Pro file. The 'get' prefix strongly suggests a read operation with no modification.
Documented attack patterns abuse exactly the kind of access get_page_setup 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 get_page_setup:
{
"version": "1",
"default": "deny",
"tools": {
"get_page_setup": {}
}
}get_page_setup is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_page_setup. It is categorised as a Read tool in the Guitar Pro MCP Server, which means it retrieves data without modifying state.
Register the Guitar Pro MCP server in PolicyLayer and add a rule for get_page_setup: 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.
get_page_setup is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_page_setup 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 get_page_setup. 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.
get_page_setup 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.