existdb_get_document

THE RISK

Low Risk

Why existdb_get_document needs a policy

This tool queries and returns existing data without side effects. It performs a GET-like operation on stored documents. No data is modified, deleted, executed, or created. The only risk is potential exposure of sensitive XML content if unauthorized access occurs, but that is a data access control issue, not a tool capability risk. Classified as Read with low severity due to minimal blast radius from tool misuse.

From the tool's definition Tool description states it 'Retrieves the XML content of a document stored in eXist-db.' The verb 'retrieves' and lack of any mention of modification, deletion, or execution indicates a read-only operation.

Documented attack patterns abuse exactly the kind of access existdb_get_document gives an agent:

POLICY

How to control existdb_get_document

PolicyLayer is an MCP gateway — it sits between your AI agents and Existdb, and nothing reaches the server without passing your rules. This is the rule we recommend for existdb_get_document:

policy.json

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

existdb_get_document is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Existdb — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Existdb tools

Destructive existdb_delete_resource Deletes a document or collection from eXist-db. Use with caution — deletion is permanent. Execute existdb_execute_query Executes an XQuery expression against a live eXist-db instance via the REST API Write existdb_store_document Stores (creates or replaces) an XML document in an eXist-db collection via PUT. Write existdb_create_collection Creates a new sub-collection inside an existing eXist-db collection. Read existdb_get_xquery_snippet Returns a ready-to-use XQuery code snippet for a common eXist-db programming pattern. Read existdb_list_collection Lists the contents of an eXist-db collection: sub-collections and XML documents Read existdb_list_namespace_functions Lists all documented functions in a given eXist-db / XQuery namespace. Read existdb_list_namespaces Returns a summary table of all available namespaces in the documentation cache,

All 12 Existdb tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about existdb_get_document

What does the existdb_get_document tool do? +

Retrieves the XML content of a document stored in eXist-db. It is categorised as a Read tool in the Existdb MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on existdb_get_document? +

Register the Existdb MCP server in PolicyLayer and add a rule for existdb_get_document: 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 Existdb. Nothing to install.

What risk level is existdb_get_document? +

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

Can I rate-limit existdb_get_document? +

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

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

existdb_get_document is provided by the Existdb MCP server (orazionelson/existdb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Existdb tool call.

Start from Existdb, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →