list_database_engines
List the database engines this node can serve — each with its data
This record as markdown: /tools/network-tenzro-tenzro/list-database-engines.md
What list_database_engines does on Tenzro Ledger MCP
AI agents call list_database_engines to retrieve information from Tenzro Ledger MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_database_engines is rated Low
This is a read-only operation that retrieves information about database engines. The verb 'list' combined with the description indicating enumeration of engines confirms it performs no side effects, reversible writes, code execution, destructive actions, or financial operations. Blast radius is minimal—an attacker learning what database engines are available on a node poses low risk.
From the tool's definition Tool name 'list_database_engines' and description 'List the database engines this node can serve — each with its data' indicate a retrieval operation that queries or enumerates available database engines and their metadata without modifying anything.
Attacks that exploit this kind of access
The rule that runs list_database_engines safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tenzro Ledger MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_database_engines, this is the rule to start with:
list_database_engines is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every list_database_engines call is checked against it from then on.
Questions about list_database_engines
List the database engines this node can serve — each with its data. It is categorised as a Read tool in the Tenzro Ledger MCP MCP Server, which means it retrieves data without modifying state.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for list_database_engines: 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 Tenzro Ledger MCP. Nothing to install.
list_database_engines 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 list_database_engines 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 list_database_engines. 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.
list_database_engines is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tenzro Ledger, and thousands of servers like it.
This server
Across the catalogue