submit_task · Jgkme/kilo Image Gen MCP: Risk & Policy

WHAT IT DOES

What submit_task does on Jgkme/kilo Image Gen

AI agents invoke submit_task to trigger actions in Jgkme/kilo Image Gen. 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.

WHY IT NEEDS A POLICY

Why submit_task needs a policy

This tool triggers an external image generation operation asynchronously via external providers (Kilo, OpenRouter, OpenAI, Gemini). It initiates a task that runs outside the local environment, classifying it as Execute. Severity is medium as it consumes API resources and may incur costs, but is not directly destructive or financial in nature.

From the tool's definition Submit an image generation task for asynchronous execution

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_task Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Jgkme/kilo Image Gen, so you can run agents against it safely.

FAQ

Questions about submit_task

What does the submit_task tool do? +

Submit an image generation task for asynchronous execution and poll it later with get_task. It is categorised as a Execute tool in the Jgkme/kilo Image Gen MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on submit_task? +

Register the Jgkme/kilo Image Gen MCP server in PolicyLayer and add a rule for submit_task: 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 Jgkme/kilo Image Gen. Nothing to install.

What risk level is submit_task? +

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

Can I rate-limit submit_task? +

Yes. Add a rate_limit block to the submit_task 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 submit_task completely? +

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

submit_task is provided by the Jgkme/kilo Image Gen MCP server (jgkme/img-gen-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.