# check_image_status

Check the status of an image generation task

Agent View of the PolicyLayer registry record for `check_image_status`. HTML page: https://policylayer.com/tools/199-mcp-mcp-kling/check-image-status

## Facts

- Tool: `check_image_status`
- Server: MCP Kling (`199-mcp/mcp-kling`) — https://policylayer.com/tools/199-mcp-mcp-kling.md
- Homepage: https://github.com/199-mcp/mcp-kling
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "check_image_status",
    "arguments": {}
  }
}
```

## Why check_image_status is rated Low

This tool retrieves status information about an existing image generation task. It queries state without modifying, deleting, or executing anything. The operation is read-only and produces no side effects, fitting the Read category.

From the tool's own definition: "Tool name 'check_image_status' and description 'Check the status of an image generation task' indicate a query/lookup operation with no side effects."

## Use case

AI agents call check_image_status to retrieve information from MCP Kling without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches MCP Kling:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_image_status": {}
  }
}
```

## Other tools on MCP Kling (11)

- `create_lipsync` — Execute — https://policylayer.com/tools/199-mcp-mcp-kling/create-lipsync.md
- `generate_image` — Execute — https://policylayer.com/tools/199-mcp-mcp-kling/generate-image.md
- `generate_image_to_video` — Execute — https://policylayer.com/tools/199-mcp-mcp-kling/generate-image-to-video.md
- `virtual_try_on` — Execute — https://policylayer.com/tools/199-mcp-mcp-kling/virtual-try-on.md
- `generate_video` — Financial — https://policylayer.com/tools/199-mcp-mcp-kling/generate-video.md
- `check_video_status` — Read — https://policylayer.com/tools/199-mcp-mcp-kling/check-video-status.md
- `get_account_balance` — Read — https://policylayer.com/tools/199-mcp-mcp-kling/get-account-balance.md
- `get_resource_packages` — Read — https://policylayer.com/tools/199-mcp-mcp-kling/get-resource-packages.md
- `list_tasks` — Read — https://policylayer.com/tools/199-mcp-mcp-kling/list-tasks.md
- `apply_video_effect` — Write — https://policylayer.com/tools/199-mcp-mcp-kling/apply-video-effect.md
- `extend_video` — Write — https://policylayer.com/tools/199-mcp-mcp-kling/extend-video.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=199-mcp-mcp-kling · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/199-mcp-mcp-kling