adb_market_install
Download and install a workflow from the marketplace. Saves to the workflows directory for immediate use with adb_workflow_run.
This record as markdown: /tools/io-github-fullread-deepadb/adb-market-install.md
What adb_market_install does on Deepadb
AI agents invoke adb_market_install to trigger actions in Deepadb. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why adb_market_install is rated High
This tool downloads external code/workflows from a marketplace and installs them locally, making them immediately executable. This constitutes an Execute-class action since it introduces and integrates external code that can then be run via adb_workflow_run. The blast radius is high because malicious or unvetted marketplace content could be installed and subsequently executed on the device.
From the tool's definition 'Download and install a workflow from the marketplace. Saves to the workflows directory for immediate use with adb_workflow_run.'
Attacks that exploit this kind of access
The rule that runs adb_market_install safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_market_install, this is the rule to start with:
adb_market_install stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_market_install call is checked against it from then on.
Questions about adb_market_install
Download and install a workflow from the marketplace. Saves to the workflows directory for immediate use with adb_workflow_run. It is categorised as a Execute tool in the Deepadb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_market_install: 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 Deepadb. Nothing to install.
adb_market_install is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the adb_market_install 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 adb_market_install. 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.
adb_market_install is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
Across the catalogue