Refresh the Zoom OAuth2 access token using the refresh token and client credentials for API access
AI agents invoke zoom_refresh_token to trigger actions in Zoom Recordings No-Auth. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external OAuth2 token refresh operation against Zoom's authentication infrastructure. It executes an API call that produces a new access token, which is a side-effectful external operation. It is not purely a read (it mutates auth state by issuing new credentials), not a write to user data, and not destructive or financial.
From the tool's definition Refresh the Zoom OAuth2 access token using the refresh token and client credentials for API access
Documented attack patterns abuse exactly the kind of access zoom_refresh_token gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zoom Recordings No-Auth, and nothing reaches the server without passing your rules. This is the rule we recommend for zoom_refresh_token:
{
"version": "1",
"default": "deny",
"tools": {
"zoom_refresh_token": {
"limits": [
{
"counter": "zoom_refresh_token_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}zoom_refresh_token stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Refresh the Zoom OAuth2 access token using the refresh token and client credentials for API access. It is categorised as a Execute tool in the Zoom Recordings No-Auth MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Zoom Recordings No-Auth MCP server in PolicyLayer and add a rule for zoom_refresh_token: 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 Zoom Recordings No-Auth. Nothing to install.
zoom_refresh_token is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the zoom_refresh_token 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_refresh_token. 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_refresh_token is provided by the Zoom Recordings No-Auth MCP server (peakmojo/mcp-server-zoom-noauth). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zoom Recordings No-Auth, 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.
4 Zoom Recordings No-Auth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.