stop_tracking · Early MCP: Risk & Policy

WHAT IT DOES

What stop_tracking does on Early MCP

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

WHY IT NEEDS A POLICY

Why stop_tracking needs a policy

Stopping a tracker modifies the state of an active time tracking session by ending it and recording the stop time. This is a reversible write operation (a new tracking session can be started, and the recorded entry can be edited or deleted), not destructive. The blast radius is medium since stopping an unintended tracker could cause loss of ongoing time tracking data.

From the tool's definition Stop the currently running tracker.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_tracking Rate-limited

stop_tracking 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": {
    "stop_tracking": {
      "limits": [
        {
          "counter": "stop_tracking_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 Early MCP, so you can run agents against it safely.

FAQ

Questions about stop_tracking

What does the stop_tracking tool do? +

Stop the currently running tracker. It is categorised as a Write tool in the Early MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on stop_tracking? +

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

What risk level is stop_tracking? +

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

Can I rate-limit stop_tracking? +

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

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

stop_tracking is provided by the Early MCP server (sakebomb/early_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

stop_tracking is one line of Early's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →