Low Risk

get_portal

Get details of a specific portal

How to control get_portal ↓

What get_portal does on Zoho Projects MCP Server

AI agents call get_portal 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.

Low Risk

Why get_portal needs a policy

This tool retrieves and queries portal details without creating, modifying, deleting, or executing any operations. It is a read-only operation that has minimal blast radius if misused—an AI agent calling it would only retrieve existing portal metadata without affecting any systems or data.

From the tool's definition Tool name 'get_portal' and description 'Get details of a specific portal' indicate retrieval of portal information with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_portal gives an agent:

How to control get_portal

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 get_portal:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_portal": {}
  }
}

get_portal is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Zoho Projects MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_portal

What does the get_portal tool do? +

Get details of a specific portal. It is categorised as a Read tool in the Zoho Projects MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_portal? +

Register the Zoho Projects MCP Server MCP server in PolicyLayer and add a rule for get_portal: 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.

What risk level is get_portal? +

get_portal is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_portal? +

Yes. Add a rate_limit block to the get_portal 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.

How do I block get_portal completely? +

Set action: deny in the PolicyLayer policy for get_portal. 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.

What MCP server provides get_portal? +

get_portal 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.

Enforce policy on every Zoho Projects MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.