pollSignupStatus
Poll the status of a signup begun via startSignup. Anonymous-callable. Possible status values: pending (user has not yet authorized — keep polling), authorized (success — response includes api_key, organization_id, user_id, user_email; the api_key is returned ONCE), consumed (already returned the...
This record as markdown: /tools/io-stablebaseline-sb/pollsignupstatus.md
What pollSignupStatus does on Stable Baseline
AI agents call pollSignupStatus to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
device_code | string | Yes | The device_code returned from startSignup. |
Parameters from the server's own tool schema.
Why pollSignupStatus is rated Low
This is fundamentally a polling/status query operation that retrieves state information. While it returns sensitive data (api_key, user credentials), the tool itself performs no write, execute, destructive, or financial operations.
From the tool's definition Tool description states it 'Poll[s] the status of a signup' and returns status values and metadata (api_key, organization_id, user_id, user_email). The operation retrieves data about an ongoing signup flow without modifying or deleting anything.
Attacks that exploit this kind of access
The rule that runs pollSignupStatus safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pollSignupStatus, this is the rule to start with:
pollSignupStatus is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every pollSignupStatus call is checked against it from then on.
Questions about pollSignupStatus
Poll the status of a signup begun via startSignup. Anonymous-callable. Possible status values: pending (user has not yet authorized — keep polling), authorized (success — response includes api_key, organization_id, user_id, user_email; the api_key is returned ONCE), consumed (already returned the api_key on a previous poll — stop polling), denied (user clicked Deny), expired (10-minute TTL exceeded — call startSignup again), not_found (invalid device_code), slow_down (you're polling faster than the interval — back off). It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
pollSignupStatus accepts 1 parameter: device_code. Required: device_code. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for pollSignupStatus: 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 Stable Baseline. Nothing to install.
pollSignupStatus 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 pollSignupStatus 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 pollSignupStatus. 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.
pollSignupStatus is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue