ae_healthcheck

Verify After Effects and aerender availability, temp scripting, and local render CLI version.

SERVERAe SOURCE@synthetic-ai/ae-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What ae_healthcheck does on Ae

AI agents use ae_healthcheck to create or update resources in Ae, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ae environment.

RISK

Why ae_healthcheck is rated Medium

An AI agent can call ae_healthcheck faster than any human can review: one bad instruction and it creates or modifies resources in Ae by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ae_healthcheck 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_healthcheck, this is the rule to start with:

ae_healthcheck Rate-limited

ae_healthcheck stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ae_healthcheck": {
      "limits": [
        {
          "counter": "ae_healthcheck_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about ae_healthcheck

What does the ae_healthcheck tool do? +

Verify After Effects and aerender availability, temp scripting, and local render CLI version. It is categorised as a Write tool in the Ae MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ae_healthcheck? +

Register the Ae MCP server in PolicyLayer and add a rule for ae_healthcheck: 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_healthcheck? +

ae_healthcheck is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ae_healthcheck? +

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

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

ae_healthcheck 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

Govern customer-ops agents →Argument validation →Scoped token →