getMigrationStats

Get model migration statistics for chat threads and messages.

SERVERNodebench SOURCEnodebench-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about getMigrationStats

What does the getMigrationStats tool do? +

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.

How do I enforce a policy on getMigrationStats? +

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.

What risk level is getMigrationStats? +

getMigrationStats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getMigrationStats? +

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.

How do I block getMigrationStats completely? +

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.

What MCP server provides getMigrationStats? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nodebench's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.