set_gradient_fill
Add or update a gradient fill on a shape group.
This record as markdown: /tools/synthetic-ai-ae-mcp/set-gradient-fill.md
What set_gradient_fill does on Ae
AI agents use set_gradient_fill 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 | — | |
compName | string | Yes | |
endColor | array | — | RGB 0..1 for end color. |
endPoint | array | — | [x, y] end point. |
groupName | string | — | |
layerName | string | Yes | |
timeoutMs | number | — | |
groupIndex | number | — | |
startColor | array | — | RGB 0..1 for start color. |
startPoint | array | — | [x, y] start point. |
projectPath | string | — | |
gradientType | string | — | linear | radial. Defaults to linear. |
Parameters from the server's own tool schema.
Why set_gradient_fill is rated Medium
An AI agent can call set_gradient_fill 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.
Risk signalsAccepts URL/endpoint input (endPoint) · High parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs set_gradient_fill 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_gradient_fill, this is the rule to start with:
set_gradient_fill 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ae, apply this rule, and every set_gradient_fill call is checked against it from then on.
Questions about set_gradient_fill
Add or update a gradient fill on a shape group. 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.
set_gradient_fill accepts 12 parameters: save, compName, endColor, endPoint, groupName, layerName, timeoutMs, groupIndex, startColor, startPoint, projectPath, gradientType. Required: compName, layerName. The full parameter table on this page comes from the server's own tool schema.
Register the Ae MCP server in PolicyLayer and add a rule for set_gradient_fill: 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.
set_gradient_fill is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_gradient_fill 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 set_gradient_fill. 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.
set_gradient_fill 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.
More on Ae, and thousands of servers like it.
This server
Across the catalogue