List all Xano instances associated with the account.
AI agents call xano_list_instances 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 simply enumerates instances without modifying, deleting, or executing any operations. It is a straightforward read operation on metadata. The blast radius is minimal—knowing what instances exist does not directly compromise data or systems, though it could inform reconnaissance in a multi-step attack. Confidence is high because the description and name are explicit about the read-only nature.
From the tool's definition Tool name 'xano_list_instances' and description 'List all Xano instances associated with the account' indicate a retrieval operation with no modification capability.
Attacks that exploit this kind of access
List all Xano instances associated with the account. 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_instances: 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_instances 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_instances 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_instances. 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_instances 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 →