example_snippet
Return curated, ready-to-adapt GDScript snippets for common Godot tasks (signals, autoload singletons, input, tweens, timers, scene changes, saving, RNG, groups, state machines, HTTP, @onready). Read-only. Omit the query to list every available topic id.
This record as markdown: /tools/breakpoint-mcp/example-snippet.md
What example_snippet does on Breakpoint
AI agents call example_snippet to retrieve information from Breakpoint 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 |
|---|---|---|---|
limit | integer | — | Max snippets to return (default 5) |
query | string | — | Topic or keywords, e.g. "tween", "save json", "connect signal". Omit to list all topics. |
Parameters from the server's own tool schema.
Why example_snippet is rated Low
Even though example_snippet only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs example_snippet 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 example_snippet, this is the rule to start with:
example_snippet 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 Breakpoint, apply this rule, and every example_snippet call is checked against it from then on.
Questions about example_snippet
Return curated, ready-to-adapt GDScript snippets for common Godot tasks (signals, autoload singletons, input, tweens, timers, scene changes, saving, RNG, groups, state machines, HTTP, @onready). Read-only. Omit the query to list every available topic id. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
example_snippet accepts 2 parameters: limit, query. 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 example_snippet: 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.
example_snippet 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 example_snippet 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 example_snippet. 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.
example_snippet 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