inspect_op_extensions_storage
Read-only: inspect what a COMP exposes — its Python storage dict (keys + values), its extension class descriptors (name, promoted flag, public members), and its custom-parameter definitions (page/name/style/default). Closes the inspect side of the reusable-component loop: use after
This record as markdown: /tools/hybridlabor-api-aos/inspect-op-extensions-storage.md
What inspect_op_extensions_storage does on Aos
AI agents call inspect_op_extensions_storage to retrieve information from Aos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why inspect_op_extensions_storage is rated Low
This tool retrieves and inspects metadata and configuration from TouchDesigner components. It performs introspection only—examining Python storage dicts, extension class descriptors, and custom-parameter definitions—with no capability to modify, delete, or execute operations. The explicit 'Read-only' designation confirms it has no side effects.
From the tool's definition Tool description explicitly states 'Read-only: inspect what a COMP exposes' and involves querying storage dictionaries, class descriptors, and parameter definitions without modification.
Attacks that exploit this kind of access
The rule that runs inspect_op_extensions_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 inspect_op_extensions_storage, this is the rule to start with:
inspect_op_extensions_storage is read-only, so it stays allowed. 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 inspect_op_extensions_storage call is checked against it from then on.
Questions about inspect_op_extensions_storage
Read-only: inspect what a COMP exposes — its Python storage dict (keys + values), its extension class descriptors (name, promoted flag, public members), and its custom-parameter definitions (page/name/style/default). Closes the inspect side of the reusable-component loop: use after. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.
Register the Aos MCP server in PolicyLayer and add a rule for inspect_op_extensions_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.
inspect_op_extensions_storage is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the inspect_op_extensions_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 inspect_op_extensions_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.
inspect_op_extensions_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