Begin an agent-driven sign-up to Stable Baseline. Anonymous-callable. Returns a verification_url and a 6-character user_code that the agent must show to the user. The user opens the URL in their browser, signs in or signs up if necessary, enters the code, and clicks Authorize. The agent meanwhile...
Part of the Stable Baseline server.
Free to start. No card required.
AI agents invoke startSignup to trigger processes or run actions in Stable Baseline. 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.
startSignup can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"tools": {
"startSignup": {
"limits": [
{
"counter": "startsignup_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Stable Baseline policy for all 184 tools.
These attack patterns abuse exactly the kind of access startSignup gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Begin an agent-driven sign-up to Stable Baseline. Anonymous-callable. Returns a verification_url and a 6-character user_code that the agent must show to the user. The user opens the URL in their browser, signs in or signs up if necessary, enters the code, and clicks Authorize. The agent meanwhile polls pollSignupStatus({device_code}) every poll_interval_seconds until the status changes to authorized, at which point it receives an api_key it can use for subsequent MCP calls. The whole flow has a 10-minute TTL.. It is categorised as a Execute tool in the Stable Baseline MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for startSignup: 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.
startSignup 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 startSignup 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 startSignup. 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.
startSignup 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.
Deterministic rules across all 184 Stable Baseline tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.