archive_expense_category · Clockify Time Tracking MCP

WHAT IT DOES

What archive_expense_category does on Clockify Time Tracking

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

WHY IT NEEDS A POLICY

Why archive_expense_category needs a policy

This tool creates or modifies data reversibly by changing an expense category's archive status. The operation is not destructive because it can be undone (restored). It does not delete data permanently, execute code, handle financial transactions directly, or retrieve data.

From the tool's definition Tool description states 'Archive or restore an expense category without deleting it.' Archiving is a reversible state change operation that modifies the status of a resource.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archive_expense_category Rate-limited

archive_expense_category 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": {
    "archive_expense_category": {
      "limits": [
        {
          "counter": "archive_expense_category_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 Clockify Time Tracking, so you can run agents against it safely.

FAQ

Questions about archive_expense_category

What does the archive_expense_category tool do? +

Archive or restore an expense category without deleting it. It is categorised as a Write tool in the Clockify Time Tracking MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on archive_expense_category? +

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

What risk level is archive_expense_category? +

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

Can I rate-limit archive_expense_category? +

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

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

archive_expense_category is provided by the Clockify Time Tracking MCP server (pypi:clockify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

archive_expense_category is one line of Clockify Time Tracking'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 →