Complete Disco signup using an email verification code. Call this after discovery_signup returns {"status": "verification_required"}. The user receives a 6-digit code by email — pass it here along with the same email address used in discovery_signup. Returns an API key on success. ...
Accepts freeform code/query input (code)
Part of the Discovery Engine MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call discovery_signup_verify to retrieve information from Discovery Engine without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though discovery_signup_verify only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
discovery_signup_verify:
rules:
- action: allowSee the full Discovery Engine policy for all 12 tools.
Agents calling read-class tools like discovery_signup_verify have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Complete Disco signup using an email verification code. Call this after discovery_signup returns {"status": "verification_required"}. The user receives a 6-digit code by email — pass it here along with the same email address used in discovery_signup. Returns an API key on success. Args: email: Email address used in the discovery_signup call. code: 6-digit verification code from the email. . It is categorised as a Read tool in the Discovery Engine MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for discovery_signup_verify. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Discovery Engine MCP server.
discovery_signup_verify is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the discovery_signup_verify rule in your Intercept 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 Intercept policy for discovery_signup_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.
discovery_signup_verify is provided by the Discovery Engine MCP server (leap-laboratories/discovery-engine). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept