close_workflow_step · Jgkme/kilo Image Gen MCP

WHAT IT DOES

What close_workflow_step does on Jgkme/kilo Image Gen

AI agents use close_workflow_step to create or update resources in Jgkme/kilo Image Gen — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jgkme/kilo Image Gen environment.

WHY IT NEEDS A POLICY

Why close_workflow_step needs a policy

The tool updates and marks workflow steps as complete, which constitutes writing/modifying data. While the operation affects workflow state management, it is reversible (steps can be reopened or modified again). This is less severe than Execute (which would trigger actual image generation or external operations) and clearly more severe than Read operations.

From the tool's definition Tool description states 'Update a workflow step and mark it complete' - this modifies the state of a workflow step record, which is a reversible data modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_workflow_step Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "close_workflow_step": {
      "limits": [
        {
          "counter": "close_workflow_step_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 close_workflow_step

What does the close_workflow_step tool do? +

Update a workflow step and mark it complete. It is categorised as a Write tool in the Jgkme/kilo Image Gen MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on close_workflow_step? +

Register the Jgkme/kilo Image Gen MCP server in PolicyLayer and add a rule for close_workflow_step: 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 close_workflow_step? +

close_workflow_step is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit close_workflow_step? +

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

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

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