Low Risk

check_video_status

Check the status of a video generation task

How to control check_video_status ↓

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

Low Risk

Even though check_video_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Kling, and nothing reaches the server without passing your rules. This is the rule we recommend for check_video_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_video_status": {}
  }
}

check_video_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP Kling — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the check_video_status tool do? +

Check the status of a video 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_video_status? +

Register the MCP Kling MCP server in PolicyLayer and add a rule for check_video_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_video_status? +

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

Can I rate-limit check_video_status? +

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

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

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

Enforce policy on every MCP Kling tool call.

Deterministic rules across all 12 MCP Kling tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

12 MCP Kling tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.