rename_mogrt_controller

Rename an Essential Graphics controller by 1-based index.

SERVERAe SOURCE@synthetic-ai/ae-mcp

Medium RISK CLASS

Category Write

Parameters 63 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/rename-mogrt-controller.md

WHAT IT DOES

What rename_mogrt_controller does on Ae

AI agents use rename_mogrt_controller 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.

Parameter	Type	Required	Description
`save`	boolean	—	Save after updating. Defaults to false.
`compName`	string	Yes	Composition name.
`timeoutMs`	number	—	Process timeout in milliseconds. Defaults to 120000.
`projectPath`	string	—	Optional absolute path to an .aep file to open first.
`controllerName`	string	Yes	New controller name.
`controllerIndex`	number	Yes	1-based controller index.

Parameters from the server's own tool schema.

RISK

Why rename_mogrt_controller is rated Medium

An AI agent can call rename_mogrt_controller 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 rename_mogrt_controller 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 rename_mogrt_controller, this is the rule to start with:

rename_mogrt_controller Rate-limited

rename_mogrt_controller 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": {
    "rename_mogrt_controller": {
      "limits": [
        {
          "counter": "rename_mogrt_controller_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 rename_mogrt_controller call is checked against it from then on.

FAQ

Questions about rename_mogrt_controller

What does the rename_mogrt_controller tool do? +

Rename an Essential Graphics controller by 1-based index. 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.

What parameters does rename_mogrt_controller accept? +

rename_mogrt_controller accepts 6 parameters: save, compName, timeoutMs, projectPath, controllerName, controllerIndex. Required: compName, controllerName, controllerIndex. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on rename_mogrt_controller? +

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

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

Can I rate-limit rename_mogrt_controller? +

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

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

rename_mogrt_controller 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 →