Batch convert multiple images to a different format.
AI agents invoke batch_convert 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.
This tool performs a batch conversion operation across multiple files, triggering external file I/O and format transformation operations. While it creates new files, it may also overwrite existing files depending on output configuration. The 'batch' nature increases blast radius. Classified as Execute because it triggers external operations (Inkscape processing) on multiple files, with potential to overwrite data.
From the tool's definition Batch convert multiple images to a different format
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_convert 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 batch_convert:
{
"version": "1",
"default": "deny",
"tools": {
"batch_convert": {
"limits": [
{
"counter": "batch_convert_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}batch_convert 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.
Batch convert multiple images to a different format. 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 batch_convert: 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.
batch_convert 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 batch_convert 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 batch_convert. 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.
batch_convert 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.