complete-migration
AI agents call complete-migration as a supporting operation in Amazon SageMaker AI MCP Server workflows.
The description is empty, so there is no direct evidence of what this tool does. The name 'complete-migration' could imply finalizing a migration process in SageMaker, which might involve write or execute actions, but without more context it's difficult to classify precisely. Lowering confidence due to lack of description.
From the tool's definition Tool name is 'complete-migration' but the description is empty or uninformative.
Attacks that exploit this kind of access
complete-migration. It is categorised as a Other tool in the Amazon SageMaker AI MCP Server MCP Server, which means it performs auxiliary operations.
Register the Amazon SageMaker AI MCP Server MCP server in PolicyLayer and add a rule for complete-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 Amazon SageMaker AI MCP Server. Nothing to install.
complete-migration is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the complete-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.
Set action: deny in the PolicyLayer policy for complete-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.
complete-migration is provided by the Amazon SageMaker AI MCP Server MCP server (awslabs.sagemaker-ai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.