getMigrationStats
Get model migration statistics for chat threads and messages.
This record as markdown: /tools/io-github-homenshum-nodebench/getmigrationstats.md
What getMigrationStats does on Nodebench
AI agents call getMigrationStats to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getMigrationStats is rated Low
This tool retrieves and queries existing migration statistics without creating, modifying, deleting, or executing operations. It is a straightforward read operation with minimal security risk. Even if an AI agent calls this tool, the worst case is unnecessary API consumption or information disclosure about model migrations, neither of which constitutes a significant security threat.
From the tool's definition Tool name and description indicate data retrieval: 'Get model migration statistics' performs querying/gathering of statistical data about chat threads and messages with no side effects.
Attacks that exploit this kind of access
The rule that runs getMigrationStats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getMigrationStats, this is the rule to start with:
getMigrationStats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every getMigrationStats call is checked against it from then on.
Questions about getMigrationStats
Get model migration statistics for chat threads and messages. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for getMigrationStats: 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 Nodebench. Nothing to install.
getMigrationStats is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getMigrationStats 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 getMigrationStats. 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.
getMigrationStats is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue