call_api

THE RISK

High Risk

Why call_api needs a policy

The tool name 'call_api' combined with the server description explicitly exposing GIMP's full PyGObject API suggests this tool can call arbitrary API functions. With access to a full programming API, it could execute arbitrary code, modify files, or perform destructive operations.

From the tool's definition Tool name 'call_api' on a server that 'Exposes GIMP's full PyGObject API for AI-powered image manipulation'

Documented attack patterns abuse exactly the kind of access call_api gives an agent:

POLICY

How to control call_api

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 call_api:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "call_api": {
      "limits": [
        {
          "counter": "call_api_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

call_api 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.

Create a free account and register Gimp — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Gimp tools

Destructive delete_layer Delete a layer from an image. Parameters: - layer_name: Name of the layer to dele Execute restart_server Drop and re-establish the connection to the GIMP MCP plugin. Use this when: - GIM Execute scale_image scale_image Execute invert_selection Invert the current selection (select what is not selected). Parameters: - image_i Execute open_image Open an image file in GIMP and create a display window. Parameters: - file_path: Execute select_by_color select_by_color Execute select_rectangle select_rectangle Execute set_active_image Raise a specific image to the front / make it active in GIMP. Parameters: - image

All 79 Gimp tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Gimp → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about call_api

What does the call_api tool do? +

call_api. 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.

How do I enforce a policy on call_api? +

Register the Gimp MCP server in PolicyLayer and add a rule for call_api: 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.

What risk level is call_api? +

call_api is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit call_api? +

Yes. Add a rate_limit block to the call_api 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.

How do I block call_api completely? +

Set action: deny in the PolicyLayer policy for call_api. 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.

What MCP server provides call_api? +

call_api 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.

Enforce policy on every Gimp tool call.

Start from Gimp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →