register_organisation_verify
Step 2 of agentic signup. Confirms the 6-digit code and creates the workspace. Returns an API key the agent should set as Authorization: Bearer <apiKey> for all subsequent FavCRM MCP calls in this session.
This record as markdown: /tools/io-favcrm-favcrm/register-organisation-verify.md
What register_organisation_verify does on FavCRM
AI agents use register_organisation_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 verification email |
requestId | string | Yes | From register_organisation_request |
Parameters from the server's own tool schema.
Why register_organisation_verify is rated Medium
This tool creates a new workspace (organisation) and issues an API key, which are reversible write operations (the workspace can potentially be deleted). It does not delete data or move money. However, severity is high because misuse could result in unauthorized workspace creation and credential issuance, giving an attacker a valid Bearer token for all subsequent FavCRM API calls.
From the tool's definition Confirms the 6-digit code and creates the workspace. Returns an API key
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs register_organisation_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 register_organisation_verify, this is the rule to start with:
register_organisation_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.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every register_organisation_verify call is checked against it from then on.
Questions about register_organisation_verify
Step 2 of agentic signup. Confirms the 6-digit code and creates the workspace. Returns an API key the agent should set as Authorization: Bearer <apiKey> for all subsequent FavCRM MCP calls in this session. 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.
register_organisation_verify accepts 2 parameters: code, requestId. Required: code, requestId. 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 register_organisation_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.
register_organisation_verify 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 register_organisation_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.
Set action: deny in the PolicyLayer policy for register_organisation_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.
register_organisation_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.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue