save_migration_mapping
Complete reviewed field list; this replaces the mapping. Preserve every intended field, identity, relationship, filter and value map. Server validates exact field schema. Empty explicitly clears the mapping.
This record as markdown: /tools/sankahq-sanka-mcp/save-migration-mapping.md
What save_migration_mapping does on Sanka MCP Server
AI agents use save_migration_mapping to create or update resources in Sanka MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sanka MCP Server environment.
Why save_migration_mapping is rated Medium
An AI agent can call save_migration_mapping faster than any human can review: one bad instruction and it creates or modifies resources in Sanka MCP Server by the hundred, each call as confident as the last.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs save_migration_mapping 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 save_migration_mapping, this is the rule to start with:
save_migration_mapping stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every save_migration_mapping call is checked against it from then on.
Questions about save_migration_mapping
Complete reviewed field list; this replaces the mapping. Preserve every intended field, identity, relationship, filter and value map. Server validates exact field schema. Empty explicitly clears the mapping. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for save_migration_mapping: 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.
save_migration_mapping 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 save_migration_mapping 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 save_migration_mapping. 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.
save_migration_mapping 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.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue