accept_team_invite_verify

Step 2 of agentic team invite acceptance. Verifies the emailed code, joins the invited user to the company, and returns a one-time MCP API key for that user.

SERVERFavCRM SOURCEhttps://api.favcrm.io/mcp

Medium RISK CLASS

Category Write

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-favcrm-favcrm/accept-team-invite-verify.md

WHAT IT DOES

What accept_team_invite_verify does on FavCRM

AI agents use accept_team_invite_verify 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
`code`	string	Yes	6-digit code from the invite email
`name`	string	—	Optional display name when creating a new user
`token`	string	Yes	Invite token returned by create_team_member_invite or from the invite link

Parameters from the server's own tool schema.

RISK

Why accept_team_invite_verify is rated Medium

This is a Write operation because it modifies data reversibly: it creates a company membership relationship and generates a new API key. While it has security implications (credentials issuance), it is not destructive (reversible via removal), not execute (doesn't run code based on arguments), and not financial.

From the tool's definition Tool description states it 'joins the invited user to the company, and returns a one-time MCP API key' — both are create/modify operations.

Risk signalsAccepts freeform code/query input (code) · Handles credentials or secrets (token)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs accept_team_invite_verify 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_verify, this is the rule to start with:

accept_team_invite_verify Rate-limited

accept_team_invite_verify 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "accept_team_invite_verify": {
      "limits": [
        {
          "counter": "accept_team_invite_verify_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every accept_team_invite_verify call is checked against it from then on.

FAQ

Questions about accept_team_invite_verify

What does the accept_team_invite_verify tool do? +

Step 2 of agentic team invite acceptance. Verifies the emailed code, joins the invited user to the company, and returns a one-time MCP API key for that user. 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.

What parameters does accept_team_invite_verify accept? +

accept_team_invite_verify accepts 3 parameters: code, name, token. Required: code, token. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on accept_team_invite_verify? +

Register the FavCRM MCP server in PolicyLayer and add a rule for accept_team_invite_verify: 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.

What risk level is accept_team_invite_verify? +

accept_team_invite_verify is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit accept_team_invite_verify? +

Yes. Add a rate_limit block to the accept_team_invite_verify 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.

How do I block accept_team_invite_verify completely? +

Set action: deny in the PolicyLayer policy for accept_team_invite_verify. 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.

What MCP server provides accept_team_invite_verify? +

accept_team_invite_verify 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.

KEEP EXPLORING

More on FavCRM, and thousands of servers like it.

This server

All 220 FavCRM tools →

Across the catalogue

team_manager_emit_decision on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →