update_comp_marker

Edit the properties of an existing composition marker (comment, duration, chapter, url). Identify the marker by index (1-based) or time.

SERVERAe SOURCE@synthetic-ai/ae-mcp

Medium RISK CLASS

Category Write

Parameters 101 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/update-comp-marker.md

WHAT IT DOES

What update_comp_marker does on Ae

AI agents use update_comp_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	—	Time in seconds to locate the marker (used if index not given)
`index`	number	—	1-based key index of the marker
`chapter`	string	—
`comment`	string	—
`compName`	string	Yes
`duration`	number	—
`timeoutMs`	number	—
`projectPath`	string	—

Parameters from the server's own tool schema.

RISK

Why update_comp_marker is rated Medium

An AI agent can call update_comp_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

RECOMMENDED RULE

The rule that runs update_comp_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 update_comp_marker, this is the rule to start with:

update_comp_marker Rate-limited

update_comp_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_comp_marker": {
      "limits": [
        {
          "counter": "update_comp_marker_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 update_comp_marker call is checked against it from then on.

FAQ

Questions about update_comp_marker

What does the update_comp_marker tool do? +

Edit the properties of an existing composition marker (comment, duration, chapter, url). Identify the marker by index (1-based) or time. 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 update_comp_marker accept? +

update_comp_marker accepts 10 parameters: url, save, time, index, chapter, comment, compName, duration, timeoutMs, projectPath. Required: compName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_comp_marker? +

Register the Ae MCP server in PolicyLayer and add a rule for update_comp_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.

What risk level is update_comp_marker? +

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

Can I rate-limit update_comp_marker? +

Yes. Add a rate_limit block to the update_comp_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.

How do I block update_comp_marker completely? +

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

What MCP server provides update_comp_marker? +

update_comp_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.

KEEP EXPLORING

More on Ae, and thousands of servers like it.

This server

All 226 Ae tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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