phalcon_create_migration · Phalcon MCP Server MCP

WHAT IT DOES

What phalcon_create_migration does on Phalcon MCP Server

AI agents invoke phalcon_create_migration to trigger actions in Phalcon MCP Server. 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 phalcon_create_migration needs a policy

Based on the tool name, this likely creates database migration files and potentially executes schema changes against a database. In the Phalcon framework, 'create migration' generates and/or runs migration scripts that modify database schema. This falls under Execute (running framework commands) and potentially Write/Destructive for schema changes. The server explicitly executes Phalcon commands directly.

From the tool's definition Tool name 'phalcon_create_migration' on a server described as 'executing Phalcon commands directly'. Empty description lowers confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

phalcon_create_migration Rate-limited

phalcon_create_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": {
    "phalcon_create_migration": {
      "limits": [
        {
          "counter": "phalcon_create_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 Phalcon MCP Server, so you can run agents against it safely.

FAQ

Questions about phalcon_create_migration

What does the phalcon_create_migration tool do? +

phalcon_create_migration. It is categorised as a Execute tool in the Phalcon MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on phalcon_create_migration? +

Register the Phalcon MCP Server MCP server in PolicyLayer and add a rule for phalcon_create_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 Phalcon MCP Server. Nothing to install.

What risk level is phalcon_create_migration? +

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

Can I rate-limit phalcon_create_migration? +

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

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

phalcon_create_migration is provided by the Phalcon MCP Server MCP server (xindong888999/phalcon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.