Edit the schema of an existing table (add, remove, or modify columns)
AI agents use edit-table-schema 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.
This tool modifies table structure irreversibly. While column removal could result in data loss, schema modification is categorized as Write rather than Destructive because: (1) the description emphasizes 'edit' and schema changes, not data destruction, (2) the blast radius is high but depends on how the AI agent uses it, and (3) a separate delete-table tool exists for destructive operations.
From the tool's definition Tool description states it can 'add, remove, or modify columns' in a table schema. Removing columns is a destructive operation that can cause data loss, but the phrasing 'edit the schema' suggests schema-level modifications rather than data deletion.
Documented attack patterns abuse exactly the kind of access edit-table-schema gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Xano MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for edit-table-schema:
{
"version": "1",
"default": "deny",
"tools": {
"edit-table-schema": {
"limits": [
{
"counter": "edit-table-schema_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit-table-schema stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Edit the schema of an existing table (add, remove, or modify columns). 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 edit-table-schema: 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.
edit-table-schema 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 edit-table-schema 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 edit-table-schema. 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.
edit-table-schema is provided by the Xano MCP Server MCP server (lowcodelocky2/xano-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Xano MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Xano MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.