List all databases (workspaces) in a specific Xano instance.
AI agents call xano_list_databases to retrieve information from Xano MCP Server for Smithery 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 information about existing databases/workspaces. It has no side effects, does not modify data, and does not execute arbitrary operations. It is a straightforward data retrieval operation with minimal risk if exposed to an AI agent, as it only reveals what databases exist in the instance.
From the tool's definition Tool name 'xano_list_databases' and description 'List all databases (workspaces) in a specific Xano instance' indicate retrieval of database metadata without modification or deletion.
Attacks that exploit this kind of access
List all databases (workspaces) in a specific Xano instance. It is categorised as a Read tool in the Xano MCP Server for Smithery MCP Server, which means it retrieves data without modifying state.
Register the Xano MCP Server for Smithery MCP server in PolicyLayer and add a rule for xano_list_databases: 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 Xano MCP Server for Smithery. Nothing to install.
xano_list_databases 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 xano_list_databases 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 xano_list_databases. 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.
xano_list_databases is provided by the Xano MCP Server for Smithery MCP server (roboulos/xano-mcp). 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 →