run_stress_test
Run a stress test on the game (spawn entities, measure performance)
This record as markdown: /tools/keeveeg-godot-mcp/run-stress-test.md
What run_stress_test does on Godot
AI agents invoke run_stress_test to trigger actions in Godot. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | Node type to spawn (default: Node2D) |
count | integer | — | Number of entities to spawn (default: 100) |
properties | object | — | Properties to set on each spawned entity |
parent_path | string | — | Parent node path for spawned entities |
Parameters from the server's own tool schema.
Why run_stress_test is rated High
This tool executes arbitrary game operations (spawning entities, performance measurement) whose effects depend on what entities are spawned and how the system responds. While the entities created by a stress test are typically temporary and the effects are reversible (unlike Destructive actions), the tool actively runs code that modifies game state and triggers external operations.
From the tool's definition Tool spawns entities and measures performance as part of a stress test on a game. The description indicates execution of code that creates game objects and monitors system behavior.
Attacks that exploit this kind of access
The rule that runs run_stress_test safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_stress_test, this is the rule to start with:
run_stress_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 Godot, apply this rule, and every run_stress_test call is checked against it from then on.
Questions about run_stress_test
Run a stress test on the game (spawn entities, measure performance). It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
run_stress_test accepts 4 parameters: type, count, properties, parent_path. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for run_stress_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 Godot. Nothing to install.
run_stress_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 run_stress_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 run_stress_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.
run_stress_test is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
Across the catalogue