List valid destination scopes for a specific item. Shows where this item can be moved to.
AI agents call list_destinations to retrieve information from Claude Code Organizer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation—it queries and returns a list of permissible destinations for an item without creating, modifying, deleting, or executing any operations. The tool has no side effects and is informational in nature, supporting the UI/UX of other tools (like move_item) rather than performing an action itself.
From the tool's definition Tool name 'list_destinations' and description 'List valid destination scopes for a specific item. Shows where this item can be moved to.' indicate a query operation that retrieves and displays information about valid move targets without modifying any data.
Documented attack patterns abuse exactly the kind of access list_destinations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code Organizer, and nothing reaches the server without passing your rules. This is the rule we recommend for list_destinations:
{
"version": "1",
"default": "deny",
"tools": {
"list_destinations": {}
}
}list_destinations is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List valid destination scopes for a specific item. Shows where this item can be moved to. It is categorised as a Read tool in the Claude Code Organizer MCP Server, which means it retrieves data without modifying state.
Register the Claude Code Organizer MCP server in PolicyLayer and add a rule for list_destinations: 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 Claude Code Organizer. Nothing to install.
list_destinations is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_destinations 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 list_destinations. 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.
list_destinations is provided by the Claude Code Organizer MCP server (mcpware/cross-code-organizer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Code Organizer, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Claude Code Organizer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.