existdb_search_functions

THE RISK

Low Risk

Why existdb_search_functions needs a policy

This tool queries function metadata to return search results. It is purely informational (search/lookup) with no side effects, no code execution, no data modification, and no destructive actions. It fits the Read category unambiguously. Severity is low because the worst outcome of misuse would be information disclosure of function names and descriptions, which are typically not sensitive in a database context.

From the tool's definition Tool performs 'full-text search across all eXist-db / XQuery function names and descriptions' – a query operation that retrieves and returns information without modifying or executing any database operations.

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

POLICY

How to control existdb_search_functions

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_search_functions:

policy.json

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

existdb_search_functions 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_document Retrieves the XML content of a document stored in eXist-db. 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.

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_search_functions

What does the existdb_search_functions tool do? +

Full-text search across all eXist-db / XQuery function names and descriptions. 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_search_functions? +

Register the Existdb MCP server in PolicyLayer and add a rule for existdb_search_functions: 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_search_functions? +

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

Can I rate-limit existdb_search_functions? +

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

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

existdb_search_functions 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 →