Delete stored tokens and generate new auth URL for re-authentication.
AI agents call reauth to permanently remove resources in Gcalendar — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The primary action is deleting stored OAuth tokens, which is an irreversible destructive operation on credential storage. While new tokens can be obtained via re-authentication, the deletion of existing tokens is permanent and could disrupt active sessions. Severity is medium because the blast radius is limited to authentication state rather than calendar data, but misuse could lock out access.
From the tool's definition 'Delete stored tokens' — the tool irreversibly removes stored authentication tokens before generating a new auth URL.
Attacks that exploit this kind of access
Delete stored tokens and generate new auth URL for re-authentication. It is categorised as a Destructive tool in the Gcalendar MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gcalendar MCP server in PolicyLayer and add a rule for reauth: 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 Gcalendar. Nothing to install.
reauth is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the reauth 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 reauth. 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.
reauth is provided by the Gcalendar MCP server (sandeepmallareddy/gcalendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →