adb_registry_installed
List all locally installed plugins with their versions and metadata. Shows which plugins have updates available in the registry.
This record as markdown: /tools/io-github-fullread-deepadb/adb-registry-installed.md
What adb_registry_installed does on Deepadb
AI agents call adb_registry_installed to retrieve information from Deepadb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why adb_registry_installed is rated Low
This tool retrieves and displays information about installed plugins and their versions. It performs a passive inspection of system state without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent would only gain visibility into what plugins are installed, which is not sensitive or harmful in typical threat models.
From the tool's definition Tool name and description: 'List all locally installed plugins with their versions and metadata. Shows which plugins have updates available in the registry.' The verbs are 'list' and 'show', which are read-only query operations with no side effects.
Attacks that exploit this kind of access
The rule that runs adb_registry_installed 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_installed, this is the rule to start with:
adb_registry_installed 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 Deepadb, apply this rule, and every adb_registry_installed call is checked against it from then on.
Questions about adb_registry_installed
List all locally installed plugins with their versions and metadata. Shows which plugins have updates available in the registry. It is categorised as a Read tool in the Deepadb MCP Server, which means it retrieves data without modifying state.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_registry_installed: 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_installed 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 adb_registry_installed 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_installed. 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_installed 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