video_studio_list_projects

List Video Studio projects.

SERVERLocalAnt SOURCEyuga-hashimoto/localant

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yuga-hashimoto-localant/video-studio-list-projects.md

WHAT IT DOES

What video_studio_list_projects does on LocalAnt

AI agents call video_studio_list_projects to retrieve information from LocalAnt without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why video_studio_list_projects is rated Low

This tool retrieves and enumerates existing Video Studio projects without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal blast radius if misused by an AI agent — only information disclosure risk.

From the tool's definition Tool name contains 'list' and description states 'List Video Studio projects' — a query operation that retrieves project data with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs video_studio_list_projects safely

PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For video_studio_list_projects, this is the rule to start with:

video_studio_list_projects Allowed

video_studio_list_projects is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "video_studio_list_projects": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every video_studio_list_projects call is checked against it from then on.

FAQ

Questions about video_studio_list_projects

What does the video_studio_list_projects tool do? +

List Video Studio projects. It is categorised as a Read tool in the LocalAnt MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on video_studio_list_projects? +

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

video_studio_list_projects is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit video_studio_list_projects? +

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

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

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

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →