wave_mark_highlight · WAVE MCP Server MCP: Risk & Policy

WHAT IT DOES

What wave_mark_highlight does on WAVE MCP Server

AI agents use wave_mark_highlight to create or update resources in WAVE MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WAVE MCP Server environment.

WHY IT NEEDS A POLICY

Why wave_mark_highlight needs a policy

The tool performs a metadata creation/modification action (marking a highlight) that is stored for later use in clipping workflows. This is a classic Write operation: it creates or modifies data in a reversible manner. An AI agent misusing this would only create unwanted highlight markers, which can be removed without consequence, resulting in low severity.

From the tool's definition Tool description states 'Mark a moment in a stream as a highlight for later clipping' — this creates metadata that flags a stream segment, which is a reversible write operation. No data is deleted, no code executes, and no financial transaction occurs.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wave_mark_highlight Rate-limited

wave_mark_highlight 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": {
    "wave_mark_highlight": {
      "limits": [
        {
          "counter": "wave_mark_highlight_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches WAVE MCP Server, so you can run agents against it safely.

FAQ

Questions about wave_mark_highlight

What does the wave_mark_highlight tool do? +

Mark a moment in a stream as a highlight for later clipping. It is categorised as a Write tool in the WAVE MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on wave_mark_highlight? +

Register the WAVE MCP Server MCP server in PolicyLayer and add a rule for wave_mark_highlight: 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 WAVE MCP Server. Nothing to install.

What risk level is wave_mark_highlight? +

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

Can I rate-limit wave_mark_highlight? +

Yes. Add a rate_limit block to the wave_mark_highlight 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 wave_mark_highlight completely? +

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

wave_mark_highlight is provided by the WAVE MCP Server MCP server (wave-av/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.