game_performance
Metricas: FPS, memoria, objetos, draw calls.
This record as markdown: /tools/mcp-godot-desenvolvimento/game-performance.md
What game_performance does on Mcp Godot Desenvolvimento
AI agents invoke game_performance 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 game_performance is rated High
game_performance triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs game_performance 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 game_performance, this is the rule to start with:
game_performance 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 game_performance call is checked against it from then on.
Questions about game_performance
Metricas: FPS, memoria, objetos, draw calls. 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 game_performance: 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.
game_performance 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 game_performance 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 game_performance. 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.
game_performance 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