get_all_component_property_names
Get all available component property names (JSON keys) from all components
This record as markdown: /tools/altium-mcp-suite/get-all-component-property-names.md
What get_all_component_property_names does on Altium-MCP-Suite
AI agents call get_all_component_property_names to retrieve information from Altium-MCP-Suite without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_all_component_property_names is rated Low
This tool retrieves and lists metadata about components in an Altium project. It has no side effects: it does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an attacker could only learn about the structure and properties of components, not alter the design or perform destructive actions. This is a straightforward Read operation.
From the tool's definition Tool description states 'Get all available component property names (JSON keys) from all components' — this is a pure data retrieval operation that queries existing properties without modification, creation, or deletion.
Attacks that exploit this kind of access
The rule that runs get_all_component_property_names 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 get_all_component_property_names, this is the rule to start with:
get_all_component_property_names is read-only, so it stays allowed. 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 get_all_component_property_names call is checked against it from then on.
Questions about get_all_component_property_names
Get all available component property names (JSON keys) from all components. It is categorised as a Read tool in the Altium-MCP-Suite MCP Server, which means it retrieves data without modifying state.
Register the Altium-MCP-Suite MCP server in PolicyLayer and add a rule for get_all_component_property_names: 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.
get_all_component_property_names 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 get_all_component_property_names 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 get_all_component_property_names. 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.
get_all_component_property_names 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