xano_rename_schema_field · Xano MCP Server MCP

WHAT IT DOES

What xano_rename_schema_field does on Xano MCP Server

AI agents use xano_rename_schema_field 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.

WHY IT NEEDS A POLICY

Why xano_rename_schema_field needs a policy

Renaming a schema field is a reversible structural modification to a database—it changes metadata and may affect dependent code/queries, but the operation can be undone by renaming back. This is less severe than Destructive (which would be irreversible deletion) but more severe than Read operations.

From the tool's definition Tool name 'xano_rename_schema_field' indicates modification of database schema structure (field renaming). The description is empty, limiting confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

xano_rename_schema_field Rate-limited

xano_rename_schema_field 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "xano_rename_schema_field": {
      "limits": [
        {
          "counter": "xano_rename_schema_field_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Xano MCP Server, so you can run agents against it safely.

FAQ

Questions about xano_rename_schema_field

What does the xano_rename_schema_field tool do? +

xano_rename_schema_field. 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.

How do I enforce a policy on xano_rename_schema_field? +

Register the Xano MCP Server MCP server in PolicyLayer and add a rule for xano_rename_schema_field: 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.

What risk level is xano_rename_schema_field? +

xano_rename_schema_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit xano_rename_schema_field? +

Yes. Add a rate_limit block to the xano_rename_schema_field 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.

How do I block xano_rename_schema_field completely? +

Set action: deny in the PolicyLayer policy for xano_rename_schema_field. 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.

What MCP server provides xano_rename_schema_field? +

xano_rename_schema_field 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.