video_studio_publish_video · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What video_studio_publish_video does on LocalAnt

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

The tool prepares or dry-runs a publish action through browser automation, which falls under Execute as it triggers external operations. The description acknowledges 'Risk 4 for real publishing,' implying it can escalate to actual publishing content externally. Even a dry-run/prepare step involves executing browser actions with potentially significant blast radius if it proceeds to real publishing.

From the tool's definition 'Dry-run or prepare a browser/manual publish action. Risk 4 for real publishing.' — involves triggering a publish action (external operation) via browser automation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

video_studio_publish_video Rate-limited

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

FAQ

Questions about video_studio_publish_video

What does the video_studio_publish_video tool do? +

Dry-run or prepare a browser/manual publish action. Risk 4 for real publishing. It is categorised as a Execute tool in the LocalAnt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on video_studio_publish_video? +

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

What risk level is video_studio_publish_video? +

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

Can I rate-limit video_studio_publish_video? +

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

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

video_studio_publish_video is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.