generate_migration · ThinAir Data MCP: Risk & Policy

WHAT IT DOES

What generate_migration does on ThinAir Data

AI agents invoke generate_migration to trigger actions in ThinAir Data. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why generate_migration needs a policy

This tool generates and likely executes ALTER TABLE migration SQL statements against a live database connection. ALTER TABLE operations can be destructive (dropping columns, changing types) and are difficult to reverse in practice despite a rollback being provided. The phrase 'Output uses the connection' implies execution against a real database, not just SQL text generation.

From the tool's definition Generate dialect-correct ALTER TABLE migration SQL + rollback from a plain-English intent

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_migration Rate-limited

generate_migration stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_migration": {
      "limits": [
        {
          "counter": "generate_migration_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about generate_migration

What does the generate_migration tool do? +

Generate dialect-correct ALTER TABLE migration SQL + rollback from a plain-English intent. Output uses the connection. It is categorised as a Execute tool in the ThinAir Data MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on generate_migration? +

Register the ThinAir Data MCP server in PolicyLayer and add a rule for generate_migration: 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 ThinAir Data. Nothing to install.

What risk level is generate_migration? +

generate_migration is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit generate_migration? +

Yes. Add a rate_limit block to the generate_migration 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 generate_migration completely? +

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

generate_migration is provided by the ThinAir Data MCP server (thinairtelematics/thinair-data). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.