Apply one effect (default Lumetri Color) + a set of numeric params to EVERY clip on a
AI agents use grade_track 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 modifies video clips by applying color grading effects and parameters across all clips in a project. This is a Write operation because: (1) it creates/modifies data (applies effects to clips), (2) the changes are reversible (effects can be removed or adjusted), and (3) it does not delete data or execute arbitrary code.
From the tool's definition Tool description states 'Apply one effect (default Lumetri Color) + a set of numeric params to EVERY clip on a' — modifies video clips by applying effects and parameters.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Apply one effect (default Lumetri Color) + a set of numeric params to EVERY clip on a. 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 grade_track: 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.
grade_track 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 grade_track 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 grade_track. 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.
grade_track 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 →