List all users in Harvest Account
AI agents call list-users 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 retrieves user information from the Harvest account without creating, modifying, or deleting any data. It is a read-only operation with minimal security impact, as user lists are typically non-sensitive operational metadata. The blast radius of misuse is low—an agent could enumerate users but cannot modify account state or access sensitive data through this tool alone.
From the tool's definition Tool name is 'list-users' and description states 'List all users in Harvest Account'. The verb 'list' indicates data retrieval with no modification or destructive capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all users 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 list-users: 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.
list-users 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 list-users 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 list-users. 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.
list-users 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 →