register_organisation_request
Step 1 of agentic signup. Sends a 6-digit verification code to the email. After the user reads the code, call register_organisation_verify with it to finish and receive an API key. Use this when a user wants to create a new FavCRM workspace from inside an MCP client.
This record as markdown: /tools/io-favcrm-favcrm/register-organisation-request.md
What register_organisation_request does on FavCRM
AI agents use register_organisation_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 |
|---|---|---|---|
email | string | Yes | Owner email — receives a 6-digit code (10 min TTL) |
country | string | — | ISO 3166-1 alpha-2 country code (HK, US, GB, ...) |
industry | string | — | Vertical — drives default templates |
timezone | string | — | IANA timezone (e.g. Asia/Hong_Kong); falls back to country default |
organisationName | string | Yes | Business / brand name (used as the first company name too) |
Parameters from the server's own tool schema.
Why register_organisation_request is rated Medium
This tool creates a new organization workspace and generates an API key, which are reversible but consequential modifications. It does not execute arbitrary code or delete data (Destructive), and while it involves account creation, it does not directly handle financial transactions. The primary action is creating/registering a new entity (organization), which is a Write operation.
From the tool's definition Sends a 6-digit verification code to the email and initiates signup process; tool description explicitly states it is 'Step 1 of agentic signup' and will 'finish and receive an API key' after verification.
Attacks that exploit this kind of access
The rule that runs register_organisation_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 register_organisation_request, this is the rule to start with:
register_organisation_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 register_organisation_request call is checked against it from then on.
Questions about register_organisation_request
Step 1 of agentic signup. Sends a 6-digit verification code to the email. After the user reads the code, call register_organisation_verify with it to finish and receive an API key. Use this when a user wants to create a new FavCRM workspace from inside an MCP client. 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_request accepts 5 parameters: email, country, industry, timezone, organisationName. Required: email, organisationName. 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_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.
register_organisation_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 register_organisation_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 register_organisation_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.
register_organisation_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