This record as markdown: /tools/synthetic-ai-ae-mcp/add-layer-marker.md
What add_layer_marker does on Ae
AI agents use add_layer_marker 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 |
|---|---|---|---|
url | string | — | |
save | boolean | — | |
time | number | Yes | Marker time in seconds. |
chapter | string | — | |
comment | string | — | |
compName | string | Yes | |
duration | number | — | |
layerName | string | Yes | |
timeoutMs | number | — | |
projectPath | string | — |
Parameters from the server's own tool schema.
Why add_layer_marker is rated Medium
An AI agent can call add_layer_marker 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 (url) · High parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs add_layer_marker 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 add_layer_marker, this is the rule to start with:
add_layer_marker 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 add_layer_marker call is checked against it from then on.
Questions about add_layer_marker
Add a marker to a layer. 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.
add_layer_marker accepts 10 parameters: url, save, time, chapter, comment, compName, duration, layerName, timeoutMs, projectPath. Required: time, 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 add_layer_marker: 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.
add_layer_marker 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 add_layer_marker 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 add_layer_marker. 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.
add_layer_marker 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