AI agents use video_studio_create_project 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.
This tool creates new files and project artifacts (manifest, script, storyboard, directories, log) but does not delete or overwrite existing data irreversibly, nor does it execute arbitrary code or move money. It is a Write operation that establishes project structure.
From the tool's definition Tool description states it 'Create[s] a Video Studio project manifest, script, storyboard, directories, and run log' — explicitly creating multiple files and data structures.
Attacks that exploit this kind of access
Create a Video Studio project manifest, script, storyboard, directories, and run log. 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.
Register the LocalAnt MCP server in PolicyLayer and add a rule for video_studio_create_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 LocalAnt. Nothing to install.
video_studio_create_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the video_studio_create_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.
Set action: deny in the PolicyLayer policy for video_studio_create_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.
video_studio_create_project 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →