Accept a workspace invitation by invite_id.
AI agents use appflowy_accept_invitation to create or update resources in AppFlowy MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AppFlowy MCP environment.
Accepting an invitation creates a new association (workspace membership) and modifies the invitations collection by marking one as accepted. This is a reversible write operation—the user could potentially leave the workspace or decline invitations in the future. It's not destructive (irreversible deletion), not financial, and not code execution.
From the tool's definition The tool 'accept a workspace invitation' performs a state change by converting an pending invitation into accepted membership, modifying the user's relationship to a workspace.
Attacks that exploit this kind of access
Accept a workspace invitation by invite_id. It is categorised as a Write tool in the AppFlowy MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AppFlowy MCP server in PolicyLayer and add a rule for appflowy_accept_invitation: 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 MCP. Nothing to install.
appflowy_accept_invitation 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_accept_invitation 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_accept_invitation. 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_accept_invitation is provided by the AppFlowy MCP server (weironz/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 →