Refresh access token using refresh token.
AI agents use appflowy_refresh_token to create or update resources in AppFlowy Cloud MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AppFlowy Cloud MCP Server environment.
This tool modifies authentication state by issuing a new access token. While not destructive (the operation is reversible and issued tokens eventually expire), it is a Write operation because it creates/updates credentials. Severity is medium because misuse could allow an attacker to maintain persistence by refreshing a stolen token, but the operation itself is part of normal OAuth flows.
From the tool's definition Tool updates access credentials via 'Refresh access token using refresh token' — a state change operation that modifies or rotates authentication tokens.
Attacks that exploit this kind of access
Refresh access token using refresh token. It is categorised as a Write tool in the AppFlowy Cloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AppFlowy Cloud MCP Server MCP server in PolicyLayer and add a rule for appflowy_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 AppFlowy Cloud MCP Server. Nothing to install.
appflowy_refresh_token is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the appflowy_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 appflowy_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.
appflowy_refresh_token is provided by the AppFlowy Cloud MCP Server MCP server (jemo69/appflowy-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 →