reveal_in_storage
Expand and reveal a file or folder in Resolve's Media Storage panel.
This record as markdown: /tools/hybridlabor-api-aos/reveal-in-storage.md
What reveal_in_storage does on Aos
AI agents use reveal_in_storage 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 reveal_in_storage is rated Medium
An AI agent can call reveal_in_storage faster than any human can review: one bad instruction and it creates or modifies resources in Aos by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs reveal_in_storage 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 reveal_in_storage, this is the rule to start with:
reveal_in_storage 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 reveal_in_storage call is checked against it from then on.
Questions about reveal_in_storage
Expand and reveal a file or folder in Resolve's Media Storage panel. 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 reveal_in_storage: 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.
reveal_in_storage 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 reveal_in_storage 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 reveal_in_storage. 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.
reveal_in_storage 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