Run diagnostic checks and identify potential issues.
AI agents invoke diagnose_issues to trigger actions in Inkscape. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool actively runs checks/diagnostics, which constitutes executing operations rather than passively reading data. While it likely doesn't modify data, it triggers external operations within Inkscape. Severity is medium due to potential side effects of running diagnostics in a graphics editing context.
From the tool's definition 'Run diagnostic checks' implies active execution of diagnostic routines against the Inkscape environment
Documented attack patterns abuse exactly the kind of access diagnose_issues gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Inkscape, and nothing reaches the server without passing your rules. This is the rule we recommend for diagnose_issues:
{
"version": "1",
"default": "deny",
"tools": {
"diagnose_issues": {
"limits": [
{
"counter": "diagnose_issues_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}diagnose_issues stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run diagnostic checks and identify potential issues. It is categorised as a Execute tool in the Inkscape MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Inkscape MCP server in PolicyLayer and add a rule for diagnose_issues: 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 Inkscape. Nothing to install.
diagnose_issues is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the diagnose_issues 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 diagnose_issues. 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.
diagnose_issues is provided by the Inkscape MCP server (sandraschi/inkscape-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Inkscape, 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.
58 Inkscape tools catalogued and risk-classified — across an index of 43,000+ MCP servers.