Get detailed information about a specific project.
AI agents call get_project_details 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.
This tool retrieves project information without modifying, deleting, or executing any operations. It is a straightforward query operation that returns data. The low severity reflects minimal risk even if an AI agent calls it repeatedly or retrieves unintended project details, as no data is altered or actions triggered.
From the tool's definition Tool name 'get_project_details' and description 'Get detailed information about a specific project' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_project_details 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 get_project_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_project_details": {}
}
}get_project_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information about a specific project. It is categorised as a Read tool in the Harvest MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Harvest MCP Server MCP server in PolicyLayer and add a rule for get_project_details: 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.
get_project_details 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 get_project_details 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 get_project_details. 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.
get_project_details 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.
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.