AI agents use adjust_levels to create or update resources in Inkscape — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Inkscape environment.
Based on the naming pattern and server context, 'adjust_levels' almost certainly adjusts image tonal levels (shadows, midtones, highlights), which is a reversible modification of graphical data. This fits the Write category. Confidence is low because the description is empty, but the sibling tools strongly suggest a consistent pattern of non-destructive image adjustments.
From the tool's definition Tool name 'adjust_levels' in context of an Inkscape vector graphics editing server with sibling tools like 'adjust_brightness_contrast', 'adjust_color_balance', 'adjust_hue_saturation' — all image/graphics adjustment operations.
Documented attack patterns abuse exactly the kind of access adjust_levels 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 adjust_levels:
{
"version": "1",
"default": "deny",
"tools": {
"adjust_levels": {
"limits": [
{
"counter": "adjust_levels_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}adjust_levels 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.
adjust_levels. It is categorised as a Write tool in the Inkscape MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Inkscape MCP server in PolicyLayer and add a rule for adjust_levels: 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.
adjust_levels 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 adjust_levels 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 adjust_levels. 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.
adjust_levels 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.