xano_create_search_index
AI agents use xano_create_search_index to create or update resources in Xano MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xano MCP Server environment.
Creating a search index modifies database schema/metadata by adding a new indexing structure. This is a Write operation because it creates a reversible database artifact that can be removed or rebuilt. It is not Execute because it doesn't run arbitrary code or queries against data. It is not Destructive because index creation doesn't delete or irreversibly alter existing data.
From the tool's definition Tool name is 'xano_create_search_index' which indicates creation of a database index artifact. The description is empty, limiting direct confirmation of exact behavior.
Attacks that exploit this kind of access
xano_create_search_index. It is categorised as a Write tool in the Xano MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xano MCP Server MCP server in PolicyLayer and add a rule for xano_create_search_index: 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. Nothing to install.
xano_create_search_index is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the xano_create_search_index 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_create_search_index. 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_create_search_index is provided by the Xano MCP Server MCP server (roboulos/simple-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 →