Low Risk

list_time_entries

list_time_entries

How to control list_time_entries ↓

AI agents call list_time_entries to retrieve information from Harvest MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The 'list_' prefix conventionally indicates retrieval without modification. No destructive, financial, or execute-level operations are implied. While the description is empty (lowering confidence slightly), the tool name and context of sibling read operations (get_*) strongly suggest this retrieves time entry data without side effects.

From the tool's definition Tool name 'list_time_entries' indicates a list/retrieval operation with no description provided. Based on naming convention and sibling tools (get_client_details, get_project_details, get_user_details, get_estimate_details), this follows the pattern of…

Documented attack patterns abuse exactly the kind of access list_time_entries 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 list_time_entries:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_time_entries": {}
  }
}

list_time_entries is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Harvest MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the list_time_entries tool do? +

list_time_entries. It is categorised as a Read tool in the Harvest MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_time_entries? +

Register the Harvest MCP Server MCP server in PolicyLayer and add a rule for list_time_entries: 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.

What risk level is list_time_entries? +

list_time_entries is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_time_entries? +

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

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

list_time_entries is provided by the Harvest MCP Server MCP server (taiste/harvest-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Harvest MCP Server tool call.

Deterministic rules across all 21 Harvest MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

21 Harvest MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.