xano_add_field_to_schema
AI agents use xano_add_field_to_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.
Adding a field to a schema modifies the database structure irreversibly in terms of application logic, though the operation itself is technically reversible (the field can be removed). This is Write rather than Destructive because it does not delete data. High severity because schema changes can break applications or cause data integrity issues if misused by an agent.
From the tool's definition Tool name 'xano_add_field_to_schema' indicates it adds/modifies a database schema. Description is empty, but the name strongly suggests structural modification of a table or database definition.
Attacks that exploit this kind of access
xano_add_field_to_schema. 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_add_field_to_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.
xano_add_field_to_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 xano_add_field_to_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 xano_add_field_to_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.
xano_add_field_to_schema 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 →