smoke_test
Smoke test rapido: valida pipeline core do MCP (ping, ClassDB, validacao, config).
This record as markdown: /tools/mcp-godot-desenvolvimento/smoke-test.md
What smoke_test does on Mcp Godot Desenvolvimento
AI agents invoke smoke_test to trigger actions in Mcp Godot Desenvolvimento. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why smoke_test is rated High
A smoke test actively triggers execution across multiple subsystems (ping, ClassDB, validation, config). It is not a passive read; it exercises the pipeline and may invoke side effects depending on what ClassDB and config validation entail. No destructive, financial, or write semantics are described, so Execute is the most severe applicable category.
From the tool's definition 'smoke_test' — 'valida pipeline core do MCP (ping, ClassDB, validacao, config)' — runs a series of validation/execution checks against the MCP core pipeline
Attacks that exploit this kind of access
The rule that runs smoke_test safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Godot Desenvolvimento, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For smoke_test, this is the rule to start with:
smoke_test stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Godot Desenvolvimento, apply this rule, and every smoke_test call is checked against it from then on.
Questions about smoke_test
Smoke test rapido: valida pipeline core do MCP (ping, ClassDB, validacao, config). It is categorised as a Execute tool in the Mcp Godot Desenvolvimento MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Godot Desenvolvimento MCP server in PolicyLayer and add a rule for smoke_test: 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 Mcp Godot Desenvolvimento. Nothing to install.
smoke_test 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 smoke_test 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 smoke_test. 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.
smoke_test is provided by the Mcp Godot Desenvolvimento MCP server (joabcostamd/mcp-godot-desenvolvimento). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Godot Desenvolvimento, and thousands of servers like it.
Across the catalogue