submit_approval_request_for_user

WHAT IT DOES

What submit_approval_request_for_user does on Clockify Time Tracking

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

This tool creates or modifies approval request records, making it a Write operation rather than Read (no data retrieval), Execute (no code/command execution), Destructive (reversible), or Financial (not moving money directly). Medium severity reflects potential workflow disruption if misused to spam requests, but limited blast radius compared to financial or destructive operations.

From the tool's definition Tool name 'submit_approval_request_for_user' indicates creation of an approval request, which is a write operation that creates new data in the system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_approval_request_for_user Rate-limited

submit_approval_request_for_user 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": {
    "submit_approval_request_for_user": {
      "limits": [
        {
          "counter": "submit_approval_request_for_user_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 submit_approval_request_for_user

What does the submit_approval_request_for_user tool do? +

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

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

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

Can I rate-limit submit_approval_request_for_user? +

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

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

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