start_time_clock
Start a time clock (timer) for tracking hours in real-time.
This record as markdown: /tools/adriantr-tripletex-mcp/start-time-clock.md
What start_time_clock does on Tripletex MCP Server
AI agents use start_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.
Why start_time_clock is rated Medium
Starting a time clock creates a new active timer entry in the system. This is a reversible write operation — the clock can be stopped or deleted. It modifies state by initiating time tracking, but has no destructive, financial, or execution implications. Severity is low as the blast radius of misuse (spurious timer started) is minimal and easily corrected.
From the tool's definition Start a time clock (timer) for tracking hours in real-time.
Attacks that exploit this kind of access
The rule that runs start_time_clock safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tripletex MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For start_time_clock, this is the rule to start with:
start_time_clock 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Tripletex MCP Server, apply this rule, and every start_time_clock call is checked against it from then on.
Questions about start_time_clock
Start a time clock (timer) for tracking hours in real-time. It is categorised as a Write tool in the Tripletex MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tripletex MCP Server MCP server in PolicyLayer and add a rule for start_time_clock: 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 Tripletex MCP Server. Nothing to install.
start_time_clock is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the start_time_clock 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.
Set action: deny in the PolicyLayer policy for start_time_clock. 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.
start_time_clock is provided by the Tripletex MCP Server MCP server (adriantr/tripletex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tripletex MCP Server, and thousands of servers like it.
This server
Across the catalogue