accept_team_invite_request
Step 1 of agentic team invite acceptance. Validates an invite token and sends a 6-digit verification code to the invited email. Then call accept_team_invite_verify with the code to join and receive an MCP API key.
This record as markdown: /tools/io-favcrm-favcrm/accept-team-invite-request.md
What accept_team_invite_request does on FavCRM
AI agents use accept_team_invite_request to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
token | string | Yes | Invite token returned by create_team_member_invite or from the invite link |
Parameters from the server's own tool schema.
Why accept_team_invite_request is rated Medium
This tool creates or modifies access credentials and team membership state. Although email transmission is reversible and the invite acceptance itself is technically reversible (users can leave teams), it grants API key access which represents a meaningful modification to the system's authorization state.
From the tool's definition Sends a 6-digit verification code to an invited email (email transmission with side effects); accepts and processes a team invite token, modifying access state by issuing an MCP API key upon verification.
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
The rule that runs accept_team_invite_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For accept_team_invite_request, this is the rule to start with:
accept_team_invite_request stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every accept_team_invite_request call is checked against it from then on.
Questions about accept_team_invite_request
Step 1 of agentic team invite acceptance. Validates an invite token and sends a 6-digit verification code to the invited email. Then call accept_team_invite_verify with the code to join and receive an MCP API key. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
accept_team_invite_request accepts 1 parameter: token. Required: token. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for accept_team_invite_request: 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 FavCRM. Nothing to install.
accept_team_invite_request 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 accept_team_invite_request 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 accept_team_invite_request. 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.
accept_team_invite_request is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue