Check whether the GIMP MCP plugin socket is reachable and responding. Returns a status dict: - connected: bool - host / port: where it tried - gimp_version: if connected successfully - error: description if not connected Use this before any other operation to verify the GIMP plugin is running. If...
AI agents call check_server to retrieve information from Gimp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a diagnostic/query tool that only reads the connection status of the GIMP MCP plugin socket. It has no side effects, does not modify any images or data, and does not execute image editing operations. The instruction to 'use this before any other operation' confirms it is a pure verification/monitoring tool with no capability to perform actions beyond information retrieval.
From the tool's definition Tool performs a status check/probe operation that 'returns a status dict' with connection information. It retrieves the state of the GIMP server (connected/host/port/gimp_version/error) without modifying any data or executing operations.
Documented attack patterns abuse exactly the kind of access check_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 check_server:
{
"version": "1",
"default": "deny",
"tools": {
"check_server": {}
}
}check_server is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check whether the GIMP MCP plugin socket is reachable and responding. Returns a status dict: - connected: bool - host / port: where it tried - gimp_version: if connected successfully - error: description if not connected Use this before any other operation to verify the GIMP plugin is running. If not connected, open GIMP and run Tools > Start MCP Server. It is categorised as a Read tool in the Gimp MCP Server, which means it retrieves data without modifying state.
Register the Gimp MCP server in PolicyLayer and add a rule for check_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.
check_server is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_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 check_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.
check_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.