Search for time entries in Harvest Account
AI agents call search-time-entries to retrieve information from Harvest Time Tracking MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search operation to retrieve and query time entry data from Harvest. It is a read-only operation with no side effects, no code execution, no data modification, and no destructive actions. The low severity reflects minimal blast radius—an AI agent misusing this tool could only access existing time tracking data without causing harm.
From the tool's definition Tool name 'search-time-entries' and description 'Search for time entries in Harvest Account' indicate a query/retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Search for time entries in Harvest Account. It is categorised as a Read tool in the Harvest Time Tracking MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Harvest Time Tracking MCP Server MCP server in PolicyLayer and add a rule for search-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 Time Tracking MCP Server. Nothing to install.
search-time-entries is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search-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.
Set action: deny in the PolicyLayer policy for search-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.
search-time-entries is provided by the Harvest Time Tracking MCP Server MCP server (mayank2424/mcp-server-harvest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →