app_press_dialog_button
A execute tool on the Altium-MCP-Suite MCP server.
This record as markdown: /tools/altium-mcp-suite/app-press-dialog-button.md
What app_press_dialog_button does on Altium-MCP-Suite
AI agents invoke app_press_dialog_button to trigger actions in Altium-MCP-Suite. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why app_press_dialog_button is rated High
Pressing dialog buttons triggers UI actions with unknown but potentially significant effects.
From the tool's definition uninformative description
Attacks that exploit this kind of access
The rule that runs app_press_dialog_button 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 app_press_dialog_button, this is the rule to start with:
app_press_dialog_button stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 app_press_dialog_button call is checked against it from then on.
Questions about app_press_dialog_button
app_press_dialog_button is a execute tool on the Altium-MCP-Suite MCP server. It is categorised as a Execute tool in the Altium-MCP-Suite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Altium-MCP-Suite MCP server in PolicyLayer and add a rule for app_press_dialog_button: 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.
app_press_dialog_button is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the app_press_dialog_button 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 app_press_dialog_button. 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.
app_press_dialog_button 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.
Across the catalogue