AI agents call migration_exchange as a supporting operation in Slack workflows.
The description is empty, so the tool's behavior cannot be determined from it alone. The name 'migration_exchange' suggests it may relate to data migration or exchanging data between systems, which could span Write or Execute categories. However, in the Slack API context, 'migration.exchange' is a method used to convert classic Slack user IDs to new workspace IDs — a Read/lookup operation.
From the tool's definition Tool name is 'migration_exchange' but description is empty or uninformative.
Attacks that exploit this kind of access
migration_exchange. It is categorised as a Other tool in the Slack MCP Server, which means it performs auxiliary operations.
Register the Slack MCP server in PolicyLayer and add a rule for migration_exchange: 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 Slack. Nothing to install.
migration_exchange 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 migration_exchange 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 migration_exchange. 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.
migration_exchange is provided by the Slack MCP server (karbassi/slack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →