resend_signup_verification

SERVERDoit SOURCE@doitintl/doit-mcp-server

High RISK CLASS

Category Execute

Parameters 21 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/doit/resend-signup-verification.md

WHAT IT DOES

What resend_signup_verification does on Doit

AI agents invoke resend_signup_verification to trigger actions in Doit. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`customerContext`	string	—	Scope the request to a specific customer by ID. Required for DoiT employees (whose token isn't tied to a single customer); omit for direct customer users.
`signupRequestId`	string	Yes

Parameters from the server's own tool schema.

RISK

Why resend_signup_verification is rated High

resend_signup_verification triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs resend_signup_verification safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Doit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resend_signup_verification, this is the rule to start with:

resend_signup_verification Rate-limited

resend_signup_verification stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resend_signup_verification": {
      "limits": [
        {
          "counter": "resend_signup_verification_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about resend_signup_verification

What does the resend_signup_verification tool do? +

Start a Cloud Intelligence trial for an organization that is not yet a DoiT customer. These operations require no API key: they are rate limited, idempotent, and provision nothing until the organization's admin verifies the request. Agents create a request and hand the returned consentUrl to the admin; the admin verifies by entering the emailed code (or signing the request on the console), after which the tenant is provisioned and the request reports its customer id. Emails a fresh 6-digit code to the requester. At most three codes per request, at least 60 seconds apart. It is categorised as a Execute tool in the Doit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does resend_signup_verification accept? +

resend_signup_verification accepts 2 parameters: customerContext, signupRequestId. Required: signupRequestId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on resend_signup_verification? +

Register the Doit MCP server in PolicyLayer and add a rule for resend_signup_verification: 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 Doit. Nothing to install.

What risk level is resend_signup_verification? +

resend_signup_verification is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit resend_signup_verification? +

Yes. Add a rate_limit block to the resend_signup_verification 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 resend_signup_verification completely? +

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

resend_signup_verification is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Doit, and thousands of servers like it.

This server

All 238 Doit tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →