export_metadata

Export clip metadata from the media pool to a CSV file.

SERVERAos SOURCE@hybridlabor-api/aos

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hybridlabor-api-aos/export-metadata.md

WHAT IT DOES

What export_metadata does on Aos

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

RISK

Why export_metadata is rated Medium

Exports data to a file; creates new CSV file without modifying source metadata or causing destruction.

From the tool's definition Export clip metadata from the media pool to a CSV file.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs export_metadata safely

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

export_metadata Rate-limited

export_metadata 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": {
    "export_metadata": {
      "limits": [
        {
          "counter": "export_metadata_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about export_metadata

What does the export_metadata tool do? +

Export clip metadata from the media pool to a CSV file. It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on export_metadata? +

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

What risk level is export_metadata? +

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

Can I rate-limit export_metadata? +

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

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

export_metadata is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →