export_click_track · Claud-Ear MCP: Risk & Policy

WHAT IT DOES

What export_click_track does on Claud-Ear

AI agents use export_click_track to create or update resources in Claud-Ear — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claud-Ear environment.

WHY IT NEEDS A POLICY

Why export_click_track needs a policy

Export operations typically create new files or data artifacts, qualifying as Write. The lack of description reduces confidence slightly, but the name strongly suggests generating a click track (reversible output file). Severity is medium because exporting audio assets has moderate blast radius—could consume storage or generate unexpected files, but effects are reversible.

From the tool's definition Tool name 'export_click_track' indicates creation and output of audio/data artifact (click track file). No description provided to clarify intent, but 'export' suggests generating and persisting new content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_click_track Rate-limited

export_click_track 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": {
    "export_click_track": {
      "limits": [
        {
          "counter": "export_click_track_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 Claud-Ear, so you can run agents against it safely.

FAQ

Questions about export_click_track

What does the export_click_track tool do? +

export_click_track. It is categorised as a Write tool in the Claud-Ear MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on export_click_track? +

Register the Claud-Ear MCP server in PolicyLayer and add a rule for export_click_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 Claud-Ear. Nothing to install.

What risk level is export_click_track? +

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

Can I rate-limit export_click_track? +

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

How do I block export_click_track completely? +

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

What MCP server provides export_click_track? +

export_click_track is provided by the Claud-Ear MCP server (null-phnix/claud-ear). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.