This record as markdown: /tools/hybridlabor-api-aos/export-document.md
What export_document does on Aos
AI agents use export_document 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.
Why export_document is rated Medium
Export operations typically create or write output files/data (Write category) rather than merely reading. Without a description, confidence is reduced. The lack of destructive language ('delete','drop','purge') and no indication of financial impact keeps severity at medium rather than high. Blast radius is moderate—exporting could leak sensitive data or create unintended outputs, but is generally reversible.
From the tool's definition Tool named 'export_document' with empty description. Based on naming convention and context of a multimedia/animation server (sibling tools include animation and camera operations), this tool likely exports or outputs document data to an external format or…
Attacks that exploit this kind of access
The rule that runs export_document 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_document, this is the rule to start with:
export_document 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every export_document call is checked against it from then on.
Questions about export_document
export_document is a write tool on the Aos MCP server. 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.
Register the Aos MCP server in PolicyLayer and add a rule for export_document: 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.
export_document 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 export_document 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 export_document. 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.
export_document 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.
More on Aos, and thousands of servers like it.
This server
Across the catalogue