set_mask_feather_opacity_expansion

Set mask feather, opacity, and expansion.

SERVERAe SOURCE@synthetic-ai/ae-mcp

Medium RISK CLASS

Category Write

Parameters 93 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/set-mask-feather-opacity-expansion.md

WHAT IT DOES

What set_mask_feather_opacity_expansion does on Ae

AI agents use set_mask_feather_opacity_expansion 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.
`feather`	array	—	Optional [x,y] feather.
`opacity`	number	—	Optional opacity 0..100.
`compName`	string	Yes	Composition name.
`maskName`	string	Yes	Mask name.
`expansion`	number	—	Optional expansion.
`layerName`	string	Yes	Layer name.
`timeoutMs`	number	—	Process timeout in milliseconds. Defaults to 120000.
`projectPath`	string	—	Optional absolute path to an .aep file to open first.

Parameters from the server's own tool schema.

RISK

Why set_mask_feather_opacity_expansion is rated Medium

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

set_mask_feather_opacity_expansion Rate-limited

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

FAQ

Questions about set_mask_feather_opacity_expansion

What does the set_mask_feather_opacity_expansion tool do? +

Set mask feather, opacity, and expansion. 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 set_mask_feather_opacity_expansion accept? +

set_mask_feather_opacity_expansion accepts 9 parameters: save, feather, opacity, compName, maskName, expansion, layerName, timeoutMs, projectPath. Required: compName, maskName, layerName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_mask_feather_opacity_expansion? +

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

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

Can I rate-limit set_mask_feather_opacity_expansion? +

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

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

set_mask_feather_opacity_expansion 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

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

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