# stop_time_clock

Stop a running time clock.

Agent View of the PolicyLayer registry record for `stop_time_clock`. HTML page: https://policylayer.com/tools/adriantr-tripletex-mcp/stop-time-clock

## Facts

- Tool: `stop_time_clock`
- Server: Tripletex MCP Server (`adriantr/tripletex-mcp`) — https://policylayer.com/tools/adriantr-tripletex-mcp.md
- Homepage: https://github.com/adriantr/tripletex-mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "stop_time_clock",
    "arguments": {}
  }
}
```

## Why stop_time_clock is rated Medium

Stopping a time clock modifies the state of an active time tracking session by ending it. This is a reversible write operation (a new time clock can be started), but it does affect ongoing time tracking data. It does not delete data, execute code, or involve financial transactions directly.

From the tool's own definition: "Stop a running time clock"

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Tripletex MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_time_clock": {
      "limits": [
        {
          "counter": "stop_time_clock_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Tripletex MCP Server (30)

- `delete_timesheet_entry` — Destructive — https://policylayer.com/tools/adriantr-tripletex-mcp/delete-timesheet-entry.md
- `approve_supplier_invoice` — Financial — https://policylayer.com/tools/adriantr-tripletex-mcp/approve-supplier-invoice.md
- `get_current_time_clock` — Read — https://policylayer.com/tools/adriantr-tripletex-mcp/get-current-time-clock.md
- `get_invoice` — Read — https://policylayer.com/tools/adriantr-tripletex-mcp/get-invoice.md
- `get_recent_activities` — Read — https://policylayer.com/tools/adriantr-tripletex-mcp/get-recent-activities.md
- `get_recent_projects` — Read — https://policylayer.com/tools/adriantr-tripletex-mcp/get-recent-projects.md
- `get_supplier_invoice` — Read — https://policylayer.com/tools/adriantr-tripletex-mcp/get-supplier-invoice.md
- `get_supplier_invoices_for_approval` — Read — https://policylayer.com/tools/adriantr-tripletex-mcp/get-supplier-invoices-for-approval.md
- `get_timesheet_entry` — Read — https://policylayer.com/tools/adriantr-tripletex-mcp/get-timesheet-entry.md
- `get_timesheet_month` — Read — https://policylayer.com/tools/adriantr-tripletex-mcp/get-timesheet-month.md
- `get_total_hours` — Read — https://policylayer.com/tools/adriantr-tripletex-mcp/get-total-hours.md
- `search_activities` — Read — https://policylayer.com/tools/adriantr-tripletex-mcp/search-activities.md
- `search_invoices` — Read — https://policylayer.com/tools/adriantr-tripletex-mcp/search-invoices.md
- `search_projects` — Read — https://policylayer.com/tools/adriantr-tripletex-mcp/search-projects.md
- `search_supplier_invoices` — Read — https://policylayer.com/tools/adriantr-tripletex-mcp/search-supplier-invoices.md
- `search_timesheet_entries` — Read — https://policylayer.com/tools/adriantr-tripletex-mcp/search-timesheet-entries.md
- `search_timesheet_weeks` — Read — https://policylayer.com/tools/adriantr-tripletex-mcp/search-timesheet-weeks.md
- `whoami` — Read — https://policylayer.com/tools/adriantr-tripletex-mcp/whoami.md
- `approve_supplier_invoices` — Write — https://policylayer.com/tools/adriantr-tripletex-mcp/approve-supplier-invoices.md
- `approve_timesheet_month` — Write — https://policylayer.com/tools/adriantr-tripletex-mcp/approve-timesheet-month.md
- `approve_timesheet_week` — Write — https://policylayer.com/tools/adriantr-tripletex-mcp/approve-timesheet-week.md
- `complete_timesheet_month` — Write — https://policylayer.com/tools/adriantr-tripletex-mcp/complete-timesheet-month.md
- `complete_timesheet_week` — Write — https://policylayer.com/tools/adriantr-tripletex-mcp/complete-timesheet-week.md
- `create_timesheet_entry` — Write — https://policylayer.com/tools/adriantr-tripletex-mcp/create-timesheet-entry.md
- `reject_supplier_invoice` — Write — https://policylayer.com/tools/adriantr-tripletex-mcp/reject-supplier-invoice.md
- `reject_supplier_invoices` — Write — https://policylayer.com/tools/adriantr-tripletex-mcp/reject-supplier-invoices.md
- `reopen_timesheet_month` — Write — https://policylayer.com/tools/adriantr-tripletex-mcp/reopen-timesheet-month.md
- `reopen_timesheet_week` — Write — https://policylayer.com/tools/adriantr-tripletex-mcp/reopen-timesheet-week.md
- `start_time_clock` — Write — https://policylayer.com/tools/adriantr-tripletex-mcp/start-time-clock.md
- `update_timesheet_entry` — Write — https://policylayer.com/tools/adriantr-tripletex-mcp/update-timesheet-entry.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=adriantr-tripletex-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/adriantr-tripletex-mcp