Returns a ready-to-use XQuery code snippet for a common eXist-db programming pattern.
AI agents call existdb_get_xquery_snippet to retrieve information from Existdb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a documentation/reference lookup tool that provides XQuery code examples. It only retrieves and returns static code snippets without executing them, modifying data, or triggering external operations. No database state is altered, no resources are deleted, and no code execution occurs. This falls squarely into the Read category as a data retrieval operation.
From the tool's definition Tool returns 'a ready-to-use XQuery code snippet for a common eXist-db programming pattern' — it retrieves and returns pre-built code templates with no side effects on the database or system.
Documented attack patterns abuse exactly the kind of access existdb_get_xquery_snippet gives an agent:
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_xquery_snippet:
{
"version": "1",
"default": "deny",
"tools": {
"existdb_get_xquery_snippet": {}
}
}existdb_get_xquery_snippet is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns a ready-to-use XQuery code snippet for a common eXist-db programming pattern. It is categorised as a Read tool in the Existdb MCP Server, which means it retrieves data without modifying state.
Register the Existdb MCP server in PolicyLayer and add a rule for existdb_get_xquery_snippet: 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.
existdb_get_xquery_snippet 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 existdb_get_xquery_snippet 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 existdb_get_xquery_snippet. 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.
existdb_get_xquery_snippet 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.
Start from Existdb, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Existdb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.