complete-migration
AI agents call complete-migration as a supporting operation in Amazon MQ MCP Server workflows.
The description is empty, so the classification is based solely on the name. 'complete-migration' could imply finalizing a broker migration in Amazon MQ, which could be a Write or Execute operation. However, without any description, confidence is very low. Given the context of Amazon MQ broker management, completing a migration likely modifies state but may not be destructive.
From the tool's definition Tool name is 'complete-migration' but description is empty or uninformative.
Attacks that exploit this kind of access
complete-migration. It is categorised as a Other tool in the Amazon MQ MCP Server MCP Server, which means it performs auxiliary operations.
Register the Amazon MQ 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 MQ 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 MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.