resubmit_approval_entries · Clockify Time Tracking MCP

WHAT IT DOES

What resubmit_approval_entries does on Clockify Time Tracking

AI agents use resubmit_approval_entries 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 resubmit_approval_entries needs a policy

Resubmitting approval entries modifies approval workflow state but does not delete data, create financial obligations, or execute arbitrary code. The effect is reversible—entries can typically be withdrawn or re-approved. While it affects time-tracking records (which may have HR/payroll implications), the action itself is a state change operation characteristic of Write category.

From the tool's definition Tool name 'resubmit_approval_entries' indicates modifying the status or metadata of time entry approval records. The sibling tool 'approve_time_off_request' on the same Clockify server suggests this tool performs reversible approval workflow updates.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resubmit_approval_entries Rate-limited

resubmit_approval_entries 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": {
    "resubmit_approval_entries": {
      "limits": [
        {
          "counter": "resubmit_approval_entries_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 resubmit_approval_entries

What does the resubmit_approval_entries tool do? +

resubmit_approval_entries. 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 resubmit_approval_entries? +

Register the Clockify Time Tracking MCP server in PolicyLayer and add a rule for resubmit_approval_entries: 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 resubmit_approval_entries? +

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

Can I rate-limit resubmit_approval_entries? +

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

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

resubmit_approval_entries 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.