Preflight safety checks for TypeORM migrations: catch data loss and locking before you merge.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
check_migrationsChecks database migrations for data loss, table locks, and deploy problems. Returns every finding with what happens, why, and a safe alternative. Run it after writing or changing a migration. Without files, it checks the migrations configured for the project, or every migrations folder.Checks database migrations for data loss, table locks, and deploy problems. Returns every finding with what happens, why, and a safe alternative. Run it after writing or changing a migration. Without files, it checks the migrations configured for the project, or every migrations folder.
No input schema was published for this tool.
explain_ruleReturns a rule's documentation: what happens, bad and safe examples, when a suppression is fine, and the PostgreSQL, MySQL, or TypeORM sources behind it.Returns a rule's documentation: what happens, bad and safe examples, when a suppression is fine, and the PostgreSQL, MySQL, or TypeORM sources behind it.
No input schema was published for this tool.
list_rulesLists every rule with its category, default severity, and databases.Lists every rule with its category, default severity, and databases.
No input schema was published for this tool.
orm-preflightPreflight safety checks for ORM migrations: data loss, locking, deploy safety.Preflight safety checks for ORM migrations: data loss, locking, deploy safety.
No input schema was published for this tool.
4 of 4 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Preflight safety checks for TypeORM migrations: catch data loss and locking before you merge.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.