adb_registry_install
Install a plugin from the community registry by name. Downloads the plugin JavaScript file into the plugins directory. Restart DeepADB to load it.
This record as markdown: /tools/io-github-fullread-deepadb/adb-registry-install.md
What adb_registry_install does on Deepadb
AI agents use adb_registry_install to create or update resources in Deepadb, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Deepadb environment.
Why adb_registry_install is rated Medium
The tool creates new files in the plugins directory and enables code execution upon restart. While it modifies state (Write), the severity is medium rather than high because the user must explicitly install and restart to trigger execution. The tool itself doesn't execute arbitrary code immediately—it stages JavaScript files for loading.
From the tool's definition Tool description explicitly states it 'Downloads the plugin JavaScript file into the plugins directory' and 'Restart DeepADB to load it'. This is creating/modifying files (plugins) on the system.
Attacks that exploit this kind of access
The rule that runs adb_registry_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_registry_install, this is the rule to start with:
adb_registry_install 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 Deepadb, apply this rule, and every adb_registry_install call is checked against it from then on.
Questions about adb_registry_install
Install a plugin from the community registry by name. Downloads the plugin JavaScript file into the plugins directory. Restart DeepADB to load it. It is categorised as a Write tool in the Deepadb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_registry_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_registry_install 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 adb_registry_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_registry_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_registry_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.
This server
Across the catalogue