move_components
A write tool on the Altium-MCP-Suite MCP server.
This record as markdown: /tools/altium-mcp-suite/move-components.md
What move_components does on Altium-MCP-Suite
AI agents use move_components to create or update resources in Altium-MCP-Suite, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Altium-MCP-Suite environment.
Why move_components is rated Medium
Moving components in a PCB design modifies project state but is reversible (components can be moved back). This is not a read-only operation, nor is it destructive, executable code, or financial. The lack of description lowers confidence slightly, but the name and peer tools (create_pcb_footprint, create_schematic_symbol) strongly suggest Write category.
From the tool's definition Tool name is 'move_components' with an empty description. Based on naming convention and context among sibling tools (which include create/get operations on PCB design objects), this tool modifies component positions on a PCB, which is a reversible write…
Attacks that exploit this kind of access
The rule that runs move_components safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Altium-MCP-Suite, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_components, this is the rule to start with:
move_components stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Altium-MCP-Suite, apply this rule, and every move_components call is checked against it from then on.
Questions about move_components
move_components is a write tool on the Altium-MCP-Suite MCP server. It is categorised as a Write tool in the Altium-MCP-Suite MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Altium-MCP-Suite MCP server in PolicyLayer and add a rule for move_components: 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 Altium-MCP-Suite. Nothing to install.
move_components is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the move_components 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 move_components. 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.
move_components is provided by the Altium-MCP-Suite MCP server (M-R-Abedini/Altium-MCP-Suite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Altium-MCP-Suite, and thousands of servers like it.
This server
Across the catalogue