inspect_migration

SERVERSanka MCP Server SOURCEsankahq/sanka-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/sankahq-sanka-mcp/inspect-migration.md

WHAT IT DOES

What inspect_migration does on Sanka MCP Server

AI agents call inspect_migration to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why inspect_migration is rated Low

Even though inspect_migration only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs inspect_migration safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For inspect_migration, this is the rule to start with:

inspect_migration Allowed

inspect_migration is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "inspect_migration": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every inspect_migration call is checked against it from then on.

FAQ

Questions about inspect_migration

What does the inspect_migration tool do? +

Read immutable resource bindings, binding_hash, mapping_hash and full stored stage reports, including inventory schema/counts/samples and mapping fields. This does not start a scan. Pin these IDs and hashes before edits. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on inspect_migration? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for inspect_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 Sanka MCP Server. Nothing to install.

What risk level is inspect_migration? +

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

Can I rate-limit inspect_migration? +

Yes. Add a rate_limit block to the inspect_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.

How do I block inspect_migration completely? +

Set action: deny in the PolicyLayer policy for inspect_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.

What MCP server provides inspect_migration? +

inspect_migration is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sanka MCP Server, and thousands of servers like it.

This server

All 385 Sanka MCP Server tools →

Across the catalogue

binary_inspect on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →