AI agents invoke restart_time_entry to trigger actions in Harvest MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an operation that restarts/resumes a time entry, triggering a state change in the Harvest API. While not irreversibly destructive (time entries can be modified afterward), it does initiate an external operation whose effects depend on which time entry is targeted. This fits Execute rather than Write because it triggers an action/workflow rather than simply creating or modifying data structures.
From the tool's definition Tool name 'restart_time_entry' indicates it triggers an operation to resume a stopped time entry. The sibling tool 'stop_time_entry' and context of time tracking confirm this performs an action with external effects.
Documented attack patterns abuse exactly the kind of access restart_time_entry gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Harvest MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for restart_time_entry:
{
"version": "1",
"default": "deny",
"tools": {
"restart_time_entry": {
"limits": [
{
"counter": "restart_time_entry_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}restart_time_entry stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
restart_time_entry. It is categorised as a Execute tool in the Harvest MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Harvest MCP Server MCP server in PolicyLayer and add a rule for restart_time_entry: 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 Harvest MCP Server. Nothing to install.
restart_time_entry is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the restart_time_entry 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 restart_time_entry. 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.
restart_time_entry is provided by the Harvest MCP Server MCP server (tgmclaughlin/harvest-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Harvest MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Harvest MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.