List tasks assigned to a project
AI agents call list-project-tasks 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 queries and retrieves task information associated with a project. It performs a read-only operation that returns data without creating, modifying, deleting, or executing any changes. The blast radius of misuse is minimal—an agent could only access task information that already exists, posing no risk of data loss, financial impact, or system compromise.
From the tool's definition Tool name 'list-project-tasks' and description 'List tasks assigned to a project' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List tasks assigned to a project. 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-project-tasks: 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-project-tasks 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-project-tasks 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-project-tasks. 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-project-tasks 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 →