test-migration
AI agents call test-migration as a supporting operation in Amazon MQ MCP Server workflows.
The description is empty, making classification uncertain. The name 'test-migration' could imply testing a migration process, which could range from Read (dry-run/validation) to Write or Execute (actually running a migration test). Given the server context (AmazonMQ broker management), migration testing could involve provisioning or reconfiguring brokers.
From the tool's definition Tool name is 'test-migration' but description is empty or uninformative.
Attacks that exploit this kind of access
test-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 test-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.
test-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 test-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 test-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.
test-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.