schema_generate_migration
Compare current schema with desired state and generate a migration file
This record as markdown: /tools/barnburner121-plugin-hub-mcp/schema-generate-migration.md
What schema_generate_migration does on Plugin Hub
AI agents use schema_generate_migration to create or update resources in Plugin Hub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Plugin Hub environment.
Why schema_generate_migration is rated Medium
An AI agent can call schema_generate_migration faster than any human can review: one bad instruction and it creates or modifies resources in Plugin Hub by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs schema_generate_migration safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Plugin Hub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For schema_generate_migration, this is the rule to start with:
schema_generate_migration 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Plugin Hub, apply this rule, and every schema_generate_migration call is checked against it from then on.
Questions about schema_generate_migration
Compare current schema with desired state and generate a migration file. It is categorised as a Write tool in the Plugin Hub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Plugin Hub MCP server in PolicyLayer and add a rule for schema_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 Plugin Hub. Nothing to install.
schema_generate_migration 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 schema_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.
Set action: deny in the PolicyLayer policy for schema_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.
schema_generate_migration is provided by the Plugin Hub MCP server (@barnburner121/plugin-hub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Plugin Hub, and thousands of servers like it.
This server
Across the catalogue