submagic_update_project · Submagic MCP: Risk & Policy

WHAT IT DOES

What submagic_update_project does on Submagic

AI agents use submagic_update_project to create or update resources in Submagic — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Submagic environment.

WHY IT NEEDS A POLICY

Why submagic_update_project needs a policy

The tool modifies existing project state (update pattern) within the Submagic video editing service. This is a reversible write operation—users can typically modify project settings, metadata, or content again. Without the description, confidence is moderate, but the naming convention and API context support Write category over Execute.

From the tool's definition Tool name "submagic_update_project" indicates modification of project data. Description is empty, but sibling tools include create, export, get, and list operations typical of a video editing API.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submagic_update_project Rate-limited

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

FAQ

Questions about submagic_update_project

What does the submagic_update_project tool do? +

submagic_update_project. It is categorised as a Write tool in the Submagic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on submagic_update_project? +

Register the Submagic MCP server in PolicyLayer and add a rule for submagic_update_project: 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_update_project? +

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

Can I rate-limit submagic_update_project? +

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

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

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