adb_result_get

Retrieve the content of a stored result handle by tool name + handle name. Returns the original content blocks as the source tool produced them. Updates the handle

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-get.md

WHAT IT DOES

What adb_result_get does on Deepadb

AI agents call adb_result_get 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_get is rated Low

adb_result_get fetches and returns existing stored result data. The action is purely informational (read); although it 'Updates the handle' (likely marking it as accessed), this is a metadata side-effect, not a destructive or consequential operation.

From the tool's definition Tool description: "Retrieve the content of a stored result handle" — the verb 'Retrieve' and the read-only nature of accessing previously stored results indicate data retrieval without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

adb_result_get Allowed

adb_result_get 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_get": {}
  }
}

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_get call is checked against it from then on.

FAQ

Questions about adb_result_get

What does the adb_result_get tool do? +

Retrieve the content of a stored result handle by tool name + handle name. Returns the original content blocks as the source tool produced them. Updates the handle. 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_get? +

Register the Deepadb MCP server in PolicyLayer and add a rule for adb_result_get: 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_get? +

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

Can I rate-limit adb_result_get? +

Yes. Add a rate_limit block to the adb_result_get 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_get completely? +

Set action: deny in the PolicyLayer policy for adb_result_get. 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_get? +

adb_result_get 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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