AI agents use create_time_entry 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.
Creating time entries modifies user work records and may affect billing, payroll, or project accounting systems. This is reversible (entries can be deleted), so it is Write rather than Destructive. Medium severity reflects that misuse could create fraudulent time records affecting financial systems, but the scope is limited to a single entry unless automated in bulk.
From the tool's definition Tool name 'create_time_entry' indicates creation of data records. Sibling tools include 'delete_time_entry' (destructive) and 'list_time_entries' (read), confirming this server manages time entry records.
Documented attack patterns abuse exactly the kind of access create_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 create_time_entry:
{
"version": "1",
"default": "deny",
"tools": {
"create_time_entry": {
"limits": [
{
"counter": "create_time_entry_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_time_entry 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.
create_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 create_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.
create_time_entry 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 create_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 create_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.
create_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.