Drop and re-establish the connection to the GIMP MCP plugin. Use this when: - GIMP was restarted after Claude Code was already running - The socket connection dropped mid-session - check_server() shows not connected but GIMP is open Returns the new connection status (same format as check_server).
AI agents invoke restart_server to trigger actions in Gimp. 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 triggers a reconnection sequence to GIMP—dropping an existing connection and establishing a new one. While not destructive to user data, it executes an operation that affects the state of inter-process communication and GIMP's availability. The action of severing and re-establishing a connection is a procedural operation whose outcome depends on system conditions, matching Execute category.
From the tool's definition Tool explicitly performs "Drop and re-establish the connection to the GIMP MCP plugin" and "check_server() shows not connected but GIMP is open".
Documented attack patterns abuse exactly the kind of access restart_server gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gimp, and nothing reaches the server without passing your rules. This is the rule we recommend for restart_server:
{
"version": "1",
"default": "deny",
"tools": {
"restart_server": {
"limits": [
{
"counter": "restart_server_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}restart_server 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.
Drop and re-establish the connection to the GIMP MCP plugin. Use this when: - GIMP was restarted after Claude Code was already running - The socket connection dropped mid-session - check_server() shows not connected but GIMP is open Returns the new connection status (same format as check_server). It is categorised as a Execute tool in the Gimp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Gimp MCP server in PolicyLayer and add a rule for restart_server: 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 Gimp. Nothing to install.
restart_server 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 restart_server 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 restart_server. 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.
restart_server is provided by the Gimp MCP server (maorcc/gimp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gimp, 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.
79 Gimp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.