AI agents call task_endding as a supporting operation in Vedit workflows.
The description is empty and the tool name 'task_endding' (likely 'task_ending') suggests it may signal or finalize a task, but without any description, the actual behavior is unknown. Given the sibling tools relate to video editing (add_bgm, clip_video, merge_videos), this could be a workflow termination signal rather than a data-modifying operation. Confidence is very low due to lack of information.
From the tool's definition Tool name is 'task_endding' with an empty description. No information is available about what this tool does.
Attacks that exploit this kind of access
task_endding. It is categorised as a Other tool in the Vedit MCP Server, which means it performs auxiliary operations.
Register the Vedit MCP server in PolicyLayer and add a rule for task_endding: 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 Vedit. Nothing to install.
task_endding is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the task_endding 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 task_endding. 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.
task_endding is provided by the Vedit MCP server (zakahan/vedit-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 →