local_marketplace_index
Scan a local package directory and write an index of installable tdmcp packages. Use it to make a folder of components browsable and installable as a simple local marketplace; the written index is what browse_library and install_library_package consume. Writes a file (destructive).
This record as markdown: /tools/hybridlabor-api-aos/local-marketplace-index.md
What local_marketplace_index does on Aos
AI agents use local_marketplace_index 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 local_marketplace_index is rated Medium
While the description acknowledges 'Writes a file (destructive)', this tool creates or overwrites an index file for a local marketplace, which is a reversible Write operation. It is not truly Destructive in the sense of irreversible deletion (no DROP, purge, or force operations on user data).
From the tool's definition Writes a file (destructive) according to the description, but the destructive effect is limited to creating/overwriting an index file in a controlled marketplace directory, not data deletion or critical system-level destructive operations.
Attacks that exploit this kind of access
The rule that runs local_marketplace_index 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 local_marketplace_index, this is the rule to start with:
local_marketplace_index 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 local_marketplace_index call is checked against it from then on.
Questions about local_marketplace_index
Scan a local package directory and write an index of installable tdmcp packages. Use it to make a folder of components browsable and installable as a simple local marketplace; the written index is what browse_library and install_library_package consume. Writes a file (destructive). 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 local_marketplace_index: 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.
local_marketplace_index 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 local_marketplace_index 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 local_marketplace_index. 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.
local_marketplace_index 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