run_video_function · Posterly MCP: Risk & Policy

WHAT IT DOES

What run_video_function does on Posterly

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

Although described as 'read-only' with no generation or credit spending, the tool executes predefined functions which falls under Execute category. The read-only nature and lack of side effects (no video generation, no credit consumption, no data modification) keeps severity low. High confidence because the description clearly indicates function execution despite being bounded and safe.

From the tool's definition Tool explicitly performs 'Run a read-only Veo helper function' with specified operations: list_input_modes, estimate_cost, or validate_request. The verb 'run' combined with 'helper function' indicates code execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_video_function Rate-limited

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

FAQ

Questions about run_video_function

What does the run_video_function tool do? +

Run a read-only Veo helper function before generation: list_input_modes, estimate_cost, or validate_request. This does not generate video or spend credits. It is categorised as a Execute tool in the Posterly MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_video_function? +

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

What risk level is run_video_function? +

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

Can I rate-limit run_video_function? +

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

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

run_video_function is provided by the Posterly MCP server (posterly-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.