ae_dialogs

List or close visible After Effects modal dialogs using Windows UI Automation.

SERVERAe SOURCE@synthetic-ai/ae-mcp

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/synthetic-ai-ae-mcp/ae-dialogs.md

WHAT IT DOES

What ae_dialogs does on Ae

AI agents call ae_dialogs to retrieve information from Ae without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`all`	boolean	—	Inspect all top-level windows instead of title-matching only. Defaults to false.
`mode`	string	—	list or close. Defaults to list.
`titlePattern`	string	—	Regex for dialog title. Defaults to ^After Effects$.
`buttonPattern`	string	—	Regex for button to invoke when closing. Defaults to Aceptar\|OK\|Accept\|Cerrar\|Close.

Parameters from the server's own tool schema.

RISK

Why ae_dialogs is rated Low

Even though ae_dialogs only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ae_dialogs safely

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

ae_dialogs Allowed

ae_dialogs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ae_dialogs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about ae_dialogs

What does the ae_dialogs tool do? +

List or close visible After Effects modal dialogs using Windows UI Automation. It is categorised as a Read tool in the Ae MCP Server, which means it retrieves data without modifying state.

What parameters does ae_dialogs accept? +

ae_dialogs accepts 4 parameters: all, mode, titlePattern, buttonPattern. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ae_dialogs? +

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

What risk level is ae_dialogs? +

ae_dialogs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ae_dialogs? +

Yes. Add a rate_limit block to the ae_dialogs 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 ae_dialogs completely? +

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

ae_dialogs is provided by the Ae MCP server (@synthetic-ai/ae-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ae, and thousands of servers like it.

This server

All 226 Ae tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →