ae_check_connection
Checks if the After Effects extension is connected to the MCP WebSocket server. Run this before executing tasks if you are unsure if After Effects is connected.
This record as markdown: /tools/ae/ae-check-connection.md
What ae_check_connection does on Ae
AI agents call ae_check_connection 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.
Why ae_check_connection is rated Low
This tool performs a connection status check, which is a read-only operation that retrieves state information without modifying anything. It has no capability to create, delete, execute, or move data. The low severity reflects that misuse poses minimal risk—an agent checking connection status cannot harm the system or workflow.
From the tool's definition Tool description states 'Checks if the After Effects extension is connected' — a pure status query with no side effects or modifications.
Attacks that exploit this kind of access
The rule that runs ae_check_connection 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_check_connection, this is the rule to start with:
ae_check_connection 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 Ae, apply this rule, and every ae_check_connection call is checked against it from then on.
Questions about ae_check_connection
Checks if the After Effects extension is connected to the MCP WebSocket server. Run this before executing tasks if you are unsure if After Effects is connected. It is categorised as a Read tool in the Ae MCP Server, which means it retrieves data without modifying state.
Register the Ae MCP server in PolicyLayer and add a rule for ae_check_connection: 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.
ae_check_connection 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 ae_check_connection 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 ae_check_connection. 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.
ae_check_connection is provided by the Ae MCP server (ae-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ae, and thousands of servers like it.
This server
Across the catalogue