xano_search_table_content
AI agents call xano_search_table_content 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.
The naming convention 'search_table_content' strongly suggests a read-only query operation over database records. No write, delete, or execute keywords present. However, confidence is moderate (0.72) rather than high due to missing description—search operations could theoretically support complex filtering that enables unauthorized data exposure at scale, warranting 'medium' severity.
From the tool's definition Tool name 'xano_search_table_content' indicates querying/searching database table data. Description is empty, limiting certainty.
Attacks that exploit this kind of access
xano_search_table_content. 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_search_table_content: 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_search_table_content 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_search_table_content 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_search_table_content. 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_search_table_content 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 →