AI agents use harvest_stop_timer to create or update resources in Harvest MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Harvest MCP Server environment.
Stopping a timer modifies the state of an existing time entry (sets the end time) but does not delete or irreversibly destroy data. It is a reversible write operation — the timer could potentially be restarted. Blast radius is low as it only affects a single time entry's running state.
From the tool's definition Stop a running timer on a time entry
Documented attack patterns abuse exactly the kind of access harvest_stop_timer 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 harvest_stop_timer:
{
"version": "1",
"default": "deny",
"tools": {
"harvest_stop_timer": {
"limits": [
{
"counter": "harvest_stop_timer_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} harvest_stop_timer 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.
Free to start. No card required.
Stop a running timer on a time entry. It is categorised as a Write tool in the Harvest MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Harvest MCP Server MCP server in PolicyLayer and add a rule for harvest_stop_timer: 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.
harvest_stop_timer 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 harvest_stop_timer 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 harvest_stop_timer. 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.
harvest_stop_timer is provided by the Harvest MCP Server MCP server (southleft/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.
21 Harvest MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.