auth_scaffold
Generate login/register/logout helpers against an installed backend SDK. FEATURE-DETECTED both ways: if the SDK provides no auth API (Photon is realtime transport), degrades to 'unsupported_feature'; if the SDK is not installed, degrades to 'install <SDK> first'. Neither writes anything. DESTRUCT...
This record as markdown: /tools/breakpoint-mcp/auth-scaffold.md
What auth_scaffold does on Breakpoint
AI agents use auth_scaffold to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
sdk | string | Yes | Which backend SDK to target |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
to_path | string | — | Destination res:// .gd path (default res://backend/auth.gd) |
overwrite | boolean | — | Overwrite if the file already exists (default false) |
Parameters from the server's own tool schema.
Why auth_scaffold is rated Medium
While the tool description uses the term 'DESTRUCTIVE,' the actual operation is file creation/generation rather than deletion or irreversible destruction. The tool writes new GDScript files (`.gd` extension) which can be modified or deleted by users. This is a Write operation (creates new files).
From the tool's definition Tool description explicitly states 'DESTRUCTIVE (writes a .gd)' — it generates and writes GDScript helper files to disk.
Attacks that exploit this kind of access
The rule that runs auth_scaffold safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For auth_scaffold, this is the rule to start with:
auth_scaffold stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every auth_scaffold call is checked against it from then on.
Questions about auth_scaffold
Generate login/register/logout helpers against an installed backend SDK. FEATURE-DETECTED both ways: if the SDK provides no auth API (Photon is realtime transport), degrades to 'unsupported_feature'; if the SDK is not installed, degrades to 'install <SDK> first'. Neither writes anything. DESTRUCTIVE (writes a .gd) — gated. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
auth_scaffold accepts 4 parameters: sdk, confirm, to_path, overwrite. Required: sdk. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for auth_scaffold: 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 Breakpoint. Nothing to install.
auth_scaffold is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the auth_scaffold 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 auth_scaffold. 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.
auth_scaffold is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue