List every configured database alias and its type.
AI agents call db_list_aliases to retrieve information from Custom MCP Database Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns configuration metadata about database aliases. It performs no write, execute, or destructive operations. The only concern is that the list of aliases might reveal sensitive information about database infrastructure to an unauthorized agent, but this is mitigated by the server's stated 'secure' design and the fact that aliases alone do not grant access to credentials or data.
From the tool's definition Tool name is 'db_list_aliases' and description states 'List every configured database alias and its type' — a retrieval operation with no modification or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every configured database alias and its type. It is categorised as a Read tool in the Custom MCP Database Server MCP Server, which means it retrieves data without modifying state.
Register the Custom MCP Database Server MCP server in PolicyLayer and add a rule for db_list_aliases: 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 Custom MCP Database Server. Nothing to install.
db_list_aliases 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 db_list_aliases 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 db_list_aliases. 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.
db_list_aliases is provided by the Custom MCP Database Server MCP server (renanlido/custom-mcp-database). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →