app_wait_for_dialog

A execute tool on the Eda Agent MCP server.

SERVEREda Agent SOURCEsalitronic/eda-agent

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eda-agent/app-wait-for-dialog.md

WHAT IT DOES

What app_wait_for_dialog does on Eda Agent

AI agents invoke app_wait_for_dialog to trigger actions in Eda Agent. 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.

RISK

Why app_wait_for_dialog is rated High

Waits for UI dialogs in Altium Designer, blocking automation—controls execution flow and timing of design operations.

From the tool's definition uninformative description; wait_for_dialog suggests automation control flow

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs app_wait_for_dialog safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Eda Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For app_wait_for_dialog, this is the rule to start with:

app_wait_for_dialog Rate-limited

app_wait_for_dialog 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "app_wait_for_dialog": {
      "limits": [
        {
          "counter": "app_wait_for_dialog_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Eda Agent, apply this rule, and every app_wait_for_dialog call is checked against it from then on.

FAQ

Questions about app_wait_for_dialog

What does the app_wait_for_dialog tool do? +

app_wait_for_dialog is a execute tool on the Eda Agent MCP server. It is categorised as a Execute tool in the Eda Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on app_wait_for_dialog? +

Register the Eda Agent MCP server in PolicyLayer and add a rule for app_wait_for_dialog: 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 Eda Agent. Nothing to install.

What risk level is app_wait_for_dialog? +

app_wait_for_dialog is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit app_wait_for_dialog? +

Yes. Add a rate_limit block to the app_wait_for_dialog 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.

How do I block app_wait_for_dialog completely? +

Set action: deny in the PolicyLayer policy for app_wait_for_dialog. 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.

What MCP server provides app_wait_for_dialog? +

app_wait_for_dialog is provided by the Eda Agent MCP server (salitronic/eda-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Eda Agent, and thousands of servers like it.

This server

All 777 Eda Agent tools → High-risk tools on this server →

Across the catalogue

browser_wait_for_element on Percepta MCP Server →wait_for_renders on Why Did You Render →qt_wait_for on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →