Add markers to the active sequence
AI agents use add_markers to create or update resources in Media-Editor-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Media-Editor-MCP environment.
This tool creates new markers in a video editing project, which is a reversible write operation. It modifies the active sequence by adding metadata without deleting or executing external code. The severity is medium because misuse could create many unwanted markers that clutter a project, but they are easily removable and don't cause permanent data loss or financial impact.
From the tool's definition Tool name 'add_markers' and description 'Add markers to the active sequence' indicate creation/modification of video editing metadata. Markers are annotations added to video sequences that modify the editing project state.
Attacks that exploit this kind of access
Add markers to the active sequence. It is categorised as a Write tool in the Media-Editor-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Media-Editor- MCP server in PolicyLayer and add a rule for add_markers: 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 Media-Editor-MCP. Nothing to install.
add_markers 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_markers 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_markers. 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_markers is provided by the Media-Editor- MCP server (nguyenph88/media-editor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →