AI agents call list_phases to retrieve information from Zoho Projects MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a query operation to retrieve and display phases or milestones associated with a project. This is a read-only operation with no side effects, no data modification, and no execution of external operations. It has minimal blast radius if misused by an AI agent—at worst, it retrieves information already accessible to the authenticated user.
From the tool's definition Tool name 'list_phases' and description 'List phases/milestones from a project' indicate a retrieval operation with no modification of data.
Documented attack patterns abuse exactly the kind of access list_phases gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zoho Projects MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_phases:
{
"version": "1",
"default": "deny",
"tools": {
"list_phases": {}
}
}list_phases 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.
List phases/milestones from a project. It is categorised as a Read tool in the Zoho Projects MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zoho Projects MCP Server MCP server in PolicyLayer and add a rule for list_phases: 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 Zoho Projects MCP Server. Nothing to install.
list_phases 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_phases 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_phases. 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_phases is provided by the Zoho Projects MCP Server MCP server (qpiai/zoho-projects-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zoho Projects MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Zoho Projects MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.