get_editor_performance
Get editor performance snapshot (FPS, timing, memory usage, object counts, render stats, physics activity)
This record as markdown: /tools/keeveeg-godot-mcp/get-editor-performance.md
What get_editor_performance does on Godot
AI agents call get_editor_performance to retrieve information from Godot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_editor_performance is rated Low
This tool queries and returns performance data without modifying any state, creating resources, executing code, or causing destructive changes. It is purely informational and diagnostic in nature. Low severity because misuse would only expose performance telemetry, not compromise system integrity or enable harmful actions.
From the tool's definition Tool retrieves performance metrics: 'Get editor performance snapshot (FPS, timing, memory usage, object counts, render stats, physics activity)'. These are read-only queries of runtime state with no side effects.
Attacks that exploit this kind of access
The rule that runs get_editor_performance 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 get_editor_performance, this is the rule to start with:
get_editor_performance 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 Godot, apply this rule, and every get_editor_performance call is checked against it from then on.
Questions about get_editor_performance
Get editor performance snapshot (FPS, timing, memory usage, object counts, render stats, physics activity). It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP server in PolicyLayer and add a rule for get_editor_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 Godot. Nothing to install.
get_editor_performance 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 get_editor_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 get_editor_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.
get_editor_performance 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.
This server
Across the catalogue