sequence_layers
Sequence a list of layers in time so each starts after the previous ends (or with an overlap).
This record as markdown: /tools/synthetic-ai-ae-mcp/sequence-layers.md
What sequence_layers does on Ae
AI agents call sequence_layers 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 |
|---|---|---|---|
save | boolean | — | |
overlap | number | — | Overlap in seconds between consecutive layers. Negative = gap. Defaults to 0. |
compName | string | Yes | |
startTime | number | — | Start time for the first layer in seconds. Defaults to comp work area start. |
timeoutMs | number | — | |
layerNames | array | Yes | Layers to sequence in order. |
projectPath | string | — |
Parameters from the server's own tool schema.
Why sequence_layers is rated Low
Even though sequence_layers 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 sequence_layers 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 sequence_layers, this is the rule to start with:
sequence_layers 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 sequence_layers call is checked against it from then on.
Questions about sequence_layers
Sequence a list of layers in time so each starts after the previous ends (or with an overlap). It is categorised as a Read tool in the Ae MCP Server, which means it retrieves data without modifying state.
sequence_layers accepts 7 parameters: save, overlap, compName, startTime, timeoutMs, layerNames, projectPath. Required: compName, layerNames. 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 sequence_layers: 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.
sequence_layers 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 sequence_layers 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 sequence_layers. 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.
sequence_layers 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