Create a Disco account and get an API key. Provide an email address to start the signup flow. If email verification is required, returns {"status": "verification_required"} — the user will receive a 6-digit code by email, then call discovery_signup_verify to complete signup and r...
Part of the Discovery Engine MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke discovery_signup to trigger processes or run actions in Discovery Engine. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
discovery_signup can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
discovery_signup:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Discovery Engine policy for all 12 tools.
Agents calling execute-class tools like discovery_signup have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
discovery_signup is one of the high-risk operations in Discovery Engine. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Create a Disco account and get an API key. Provide an email address to start the signup flow. If email verification is required, returns {"status": "verification_required"} — the user will receive a 6-digit code by email, then call discovery_signup_verify to complete signup and receive the API key. The free tier (10 credits/month, unlimited public runs) is active immediately. No authentication required. Returns 409 if the email is already registered. Args: email: Email address for the new account. name: Display name (optional — defaults to email local part). . It is categorised as a Execute tool in the Discovery Engine MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for discovery_signup. 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 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the discovery_signup 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. 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 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