Low Risk

list_estimate_messages

list_estimate_messages

How to control list_estimate_messages ↓

AI agents call list_estimate_messages 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 strongly suggests a retrieval operation that queries data without side effects. Even though the description is empty (lowering confidence slightly), the tool name and its position among other tools (alongside create, delete, and change operations) indicates this lists estimate messages for informational purposes. Risk is minimal if an AI agent calls this tool.

From the tool's definition Tool name 'list_estimate_messages' indicates a retrieval/listing operation. No description provided, but naming convention (list_*) and context within a time-tracking/billing system (Harvest) suggest querying existing estimate-related messages without…

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

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

list_estimate_messages 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_estimate_messages tool do? +

list_estimate_messages. 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_estimate_messages? +

Register the Harvest MCP Server MCP server in PolicyLayer and add a rule for list_estimate_messages: 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_estimate_messages? +

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

Can I rate-limit list_estimate_messages? +

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

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

list_estimate_messages 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.