AI agents use import_from_json 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.
This tool creates or modifies Guitar Pro file data by importing from an external JSON source. While the description is empty, the name and server context clearly indicate it performs a Write operation (reversible modification of file data). It is not Destructive because import does not delete existing data irreversibly, nor Execute/Financial/Read.
From the tool's definition Tool name 'import_from_json' indicates data import/creation functionality. Server description states it provides tools for 'modifying and saving Guitar Pro files.' Sibling tools like 'create_new_gp_song' and 'add_*' confirm this is a write-capable server.
Documented attack patterns abuse exactly the kind of access import_from_json 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 import_from_json:
{
"version": "1",
"default": "deny",
"tools": {
"import_from_json": {
"limits": [
{
"counter": "import_from_json_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_from_json 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.
import_from_json. 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 import_from_json: 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.
import_from_json 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 import_from_json 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 import_from_json. 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.
import_from_json 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.