This record as markdown: /tools/sagemcp-sagemcp/zoom-get-user.md
What zoom_get_user does on Sage MCP
AI agents call zoom_get_user to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why zoom_get_user is rated Low
This tool retrieves user profile data from Zoom without modifying, creating, or deleting anything. It has no side effects and poses minimal risk—the worst outcome is exposure of user profile information (names, email addresses, etc.), which is a low-severity information disclosure rather than system compromise or data destruction. Confidence is high because the description is explicit and unambiguous.
From the tool's definition Tool name 'zoom_get_user' and description 'Get user profile information' indicate a retrieval operation with no side effects. The verb 'get' and 'profile information' (a read-only data query) confirm this is a Read category tool.
Attacks that exploit this kind of access
The rule that runs zoom_get_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zoom_get_user, this is the rule to start with:
zoom_get_user is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every zoom_get_user call is checked against it from then on.
Questions about zoom_get_user
Get user profile information. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for zoom_get_user: 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 Sage MCP. Nothing to install.
zoom_get_user 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 zoom_get_user 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 zoom_get_user. 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.
zoom_get_user is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sage, and thousands of servers like it.
This server
Across the catalogue