AI agents call get_module_data to retrieve information from MCP-Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval operation with no side effects. The 'Fetch' action and context among sibling tools confirm it performs read-only queries against Zoho CRM. Severity is medium rather than low because CRM data often contains sensitive business and customer information; unauthorized or misdirected queries could expose PII or confidential records, though the tool itself is not destructive or financial.
From the tool's definition Tool name is 'get_module_data' and description states 'Fetch data from Zoho CRM modules'. The verb 'Fetch' indicates data retrieval without modification.
Documented attack patterns abuse exactly the kind of access get_module_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_module_data:
{
"version": "1",
"default": "deny",
"tools": {
"get_module_data": {}
}
} get_module_data 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.
Fetch data from Zoho CRM modules. It is categorised as a Read tool in the MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the MCP-Server MCP server in PolicyLayer and add a rule for get_module_data: 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 MCP-Server. Nothing to install.
get_module_data 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_module_data 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_module_data. 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_module_data is provided by the MCP-Server MCP server (officehub-tech-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from 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.
9 MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.