leaderboard_scaffold
Generate submit/fetch leaderboard helpers against an installed backend SDK. FEATURE-DETECTED both ways: if the SDK provides no leaderboard API (Photon is realtime transport), degrades to 'unsupported_feature'; if the SDK is not installed, degrades to 'install <SDK> first'. Neither writes anything...
This record as markdown: /tools/breakpoint-mcp/leaderboard-scaffold.md
What leaderboard_scaffold does on Breakpoint
AI agents use leaderboard_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/leaderboard.gd) |
overwrite | boolean | — | Overwrite if the file already exists (default false) |
leaderboard_name | string | — | Leaderboard id / statistic name baked into the script (default 'main') |
Parameters from the server's own tool schema.
Why leaderboard_scaffold is rated Medium
The tool generates and writes GDScript code files (.gd) to disk, which is reversible data modification. While the description uses the word 'DESTRUCTIVE', the actual operation is file creation/writing, not irreversible deletion. The gating mechanism and feature-detection logic suggest this is a scaffolding utility that creates new files rather than destroying existing ones.
From the tool's definition 'generates submit/fetch leaderboard helpers' and 'writes a .gd' (GDScript file generation). The description explicitly states 'DESTRUCTIVE (writes a .gd) — gated', indicating file creation/modification.
Attacks that exploit this kind of access
The rule that runs leaderboard_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 leaderboard_scaffold, this is the rule to start with:
leaderboard_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 leaderboard_scaffold call is checked against it from then on.
Questions about leaderboard_scaffold
Generate submit/fetch leaderboard helpers against an installed backend SDK. FEATURE-DETECTED both ways: if the SDK provides no leaderboard 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.
leaderboard_scaffold accepts 5 parameters: sdk, confirm, to_path, overwrite, leaderboard_name. 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 leaderboard_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.
leaderboard_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 leaderboard_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 leaderboard_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.
leaderboard_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