auth_scaffold
Generate login/register/logout helpers against an installed backend SDK. FEATURE-DETECTED both ways: if the SDK
This record as markdown: /tools/godot-breakpoint-mcp/auth-scaffold.md
What auth_scaffold does on Godot Breakpoint
AI agents use auth_scaffold to create or update resources in Godot Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Breakpoint environment.
Why auth_scaffold is rated Medium
This tool generates authentication scaffolding code, which creates new files or modifies the project structure reversibly. While it doesn't delete data and isn't financial, it does create/write new code. The severity is medium because misuse could create insecure authentication logic or unintended authentication flows, but the effects are reversible (generated code can be edited or deleted).
From the tool's definition Tool name 'auth_scaffold' and description 'Generate login/register/logout helpers' indicate the tool creates or generates new code/authentication helpers.
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 Godot 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 Godot 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. It is categorised as a Write tool in the Godot Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot 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 Godot 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 Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot Breakpoint, and thousands of servers like it.
This server
Across the catalogue