submagic_create_magic_clips · Submagic MCP: Risk & Policy

WHAT IT DOES

What submagic_create_magic_clips does on Submagic

AI agents invoke submagic_create_magic_clips to trigger actions in Submagic. 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 submagic_create_magic_clips needs a policy

Based on the tool name, it likely triggers an AI-driven video clip creation process (an external operation), placing it in the Execute category. The 'create' verb and context of a video editing API suggest it initiates a processing job. However, with no description available, confidence is low. Severity is medium as misuse could consume API credits or generate unwanted content.

From the tool's definition Tool name 'submagic_create_magic_clips' suggests creation/generation of video clips, but the description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submagic_create_magic_clips Rate-limited

submagic_create_magic_clips 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": {
    "submagic_create_magic_clips": {
      "limits": [
        {
          "counter": "submagic_create_magic_clips_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 Submagic, so you can run agents against it safely.

FAQ

Questions about submagic_create_magic_clips

What does the submagic_create_magic_clips tool do? +

submagic_create_magic_clips. It is categorised as a Execute tool in the Submagic MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on submagic_create_magic_clips? +

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

What risk level is submagic_create_magic_clips? +

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

Can I rate-limit submagic_create_magic_clips? +

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

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

submagic_create_magic_clips is provided by the Submagic MCP server (sidart10/submagic-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.