xano_create_table
AI agents use xano_create_table 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.
The tool creates new database schema objects (tables) in a Xano database. This is a Write action because it adds new data structures that can be subsequently modified or deleted. While not destructive itself, a rogue creation of many tables could degrade database performance or consume resources, warranting medium severity. Confidence is reduced slightly due to empty description, but the name and context are clear.
From the tool's definition Tool name 'xano_create_table' indicates creation of a new database table. Related sibling tools include 'xano_bulk_delete_records' and 'xano_bulk_update_records', confirming this server manages database schemas and data.
Attacks that exploit this kind of access
xano_create_table. 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_table: 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_table 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_table 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_table. 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_table 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 →