Run database migration for Frappe apps
Part of the Frappe Dev MCP Server server.
Free to start. No card required.
AI agents use frappe_migrate_database to create or modify resources in Frappe Dev MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call frappe_migrate_database repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Frappe Dev MCP Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"frappe_migrate_database": {
"limits": [
{
"counter": "frappe_migrate_database_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Frappe Dev MCP Server policy for all 29 tools.
These attack patterns abuse exactly the kind of access frappe_migrate_database gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Run database migration for Frappe apps. It is categorised as a Write tool in the Frappe Dev MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Frappe Dev MCP Server MCP server in PolicyLayer and add a rule for frappe_migrate_database: 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 Frappe Dev MCP Server. Nothing to install.
frappe_migrate_database 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 frappe_migrate_database 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 frappe_migrate_database. 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.
frappe_migrate_database is provided by the Frappe Dev MCP Server MCP server (frappe-dev-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Frappe Dev MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.