check_image_status

Check the status of an image generation task

SERVERMCP Kling SOURCE199-mcp/mcp-kling

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/199-mcp-mcp-kling/check-image-status.md

WHAT IT DOES

What check_image_status does on MCP Kling

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.

RISK

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_image_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Kling, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_image_status, this is the rule to start with:

check_image_status Allowed

check_image_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Kling, apply this rule, and every check_image_status call is checked against it from then on.

FAQ

Questions about check_image_status

What does the check_image_status tool do? +

Check the status of an image generation task. It is categorised as a Read tool in the MCP Kling MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_image_status? +

Register the MCP Kling MCP server in PolicyLayer and add a rule for check_image_status: 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 MCP Kling. Nothing to install.

What risk level is check_image_status? +

check_image_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_image_status? +

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

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

check_image_status is provided by the MCP Kling MCP server (199-mcp/mcp-kling). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Kling, and thousands of servers like it.

This server

All 12 MCP Kling tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server →analyze_image on Percepta MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →