video_studio_generate_assets · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What video_studio_generate_assets does on LocalAnt

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

WHY IT NEEDS A POLICY

Why video_studio_generate_assets needs a policy

This tool creates (writes) image assets in PNG format on the local system. It is reversible—generated files can be deleted—so it does not qualify as Destructive. There is no code execution, external command triggering, or financial impact. The severity is low because generating local asset files has minimal blast radius; worst case an AI agent fills disk space with unwanted PNG files, which is recoverable.

From the tool's definition The tool description states it 'Generate[s]... PNG assets', which is a write operation creating new files locally. The word 'generate' indicates creation of data/files without deletion or side effects beyond file creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

video_studio_generate_assets Rate-limited

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

FAQ

Questions about video_studio_generate_assets

What does the video_studio_generate_assets tool do? +

Generate free local scene PNG assets. It is categorised as a Write tool in the LocalAnt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on video_studio_generate_assets? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for video_studio_generate_assets: 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_generate_assets? +

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

Can I rate-limit video_studio_generate_assets? +

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

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

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