adb_result_list

List all result handles currently stored in this session. Returns metadata for each: tool, name, size, creation/expiry/last-access times. Use the URIs (

SERVERDeepadb SOURCEdeepadb

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-fullread-deepadb/adb-result-list.md

WHAT IT DOES

What adb_result_list does on Deepadb

AI agents call adb_result_list 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.

RISK

Why adb_result_list is rated Low

This is a data retrieval tool that queries stored session result metadata. It has no side effects, does not modify or delete data, and does not execute commands. The capability to access URIs for results is informational only. The blast radius if misused by an AI agent is minimal—an agent could only read metadata about previously-stored results.

From the tool's definition Tool name and description clearly indicate listing/querying operation: 'List all result handles currently stored in this session. Returns metadata for each'. No mention of modification, deletion, or execution of commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_result_list 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_result_list, this is the rule to start with:

adb_result_list Allowed

adb_result_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adb_result_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_result_list call is checked against it from then on.

FAQ

Questions about adb_result_list

What does the adb_result_list tool do? +

List all result handles currently stored in this session. Returns metadata for each: tool, name, size, creation/expiry/last-access times. Use the URIs (. It is categorised as a Read tool in the Deepadb MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on adb_result_list? +

Register the Deepadb MCP server in PolicyLayer and add a rule for adb_result_list: 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.

What risk level is adb_result_list? +

adb_result_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit adb_result_list? +

Yes. Add a rate_limit block to the adb_result_list 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.

How do I block adb_result_list completely? +

Set action: deny in the PolicyLayer policy for adb_result_list. 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.

What MCP server provides adb_result_list? +

adb_result_list 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.

KEEP EXPLORING

More on Deepadb, and thousands of servers like it.

This server

All 205 Deepadb tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →