get_layer_blend_mode
Return the current blending mode of a layer as a string (e.g. 'BlendingMode.NORMAL', 'BlendingMode.MULTIPLY').
This record as markdown: /tools/synthetic-ai-ae-mcp/get-layer-blend-mode.md
What get_layer_blend_mode does on Ae
AI agents call get_layer_blend_mode 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
compName | string | Yes | |
layerName | string | Yes | |
timeoutMs | number | — | |
projectPath | string | — |
Parameters from the server's own tool schema.
Why get_layer_blend_mode is rated Low
Even though get_layer_blend_mode only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_layer_blend_mode 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 get_layer_blend_mode, this is the rule to start with:
get_layer_blend_mode 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 get_layer_blend_mode call is checked against it from then on.
Questions about get_layer_blend_mode
Return the current blending mode of a layer as a string (e.g. 'BlendingMode.NORMAL', 'BlendingMode.MULTIPLY'). It is categorised as a Read tool in the Ae MCP Server, which means it retrieves data without modifying state.
get_layer_blend_mode accepts 4 parameters: compName, layerName, timeoutMs, projectPath. 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 get_layer_blend_mode: 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.
get_layer_blend_mode 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 get_layer_blend_mode 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 get_layer_blend_mode. 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.
get_layer_blend_mode 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