get_performance_monitors
Get all performance monitor values (FPS, memory, physics, rendering, navigation)
This record as markdown: /tools/keeveeg-godot-mcp/get-performance-monitors.md
What get_performance_monitors does on Godot
AI agents call get_performance_monitors 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
monitors | array | — | Filter to specific monitor names only (e.g. ["time/fps", "memory/static"]). Returns all monitors if omitted. |
Parameters from the server's own tool schema.
Why get_performance_monitors is rated Low
This tool retrieves performance telemetry and monitoring data from the Godot engine runtime. It only reads existing performance metrics without modifying, executing, or deleting anything. The worst-case misuse (an agent repeatedly querying for performance data) causes no harm beyond potential minor resource consumption from polling. This is a straightforward Read category operation with low severity.
From the tool's definition Tool description states 'Get all performance monitor values (FPS, memory, physics, rendering, navigation)' - uses 'Get' indicating retrieval with 'monitor values' indicating observational/telemetry data only.
Attacks that exploit this kind of access
The rule that runs get_performance_monitors 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_performance_monitors, this is the rule to start with:
get_performance_monitors 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_performance_monitors call is checked against it from then on.
Questions about get_performance_monitors
Get all performance monitor values (FPS, memory, physics, rendering, navigation). It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
get_performance_monitors accepts 1 parameter: monitors. 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 get_performance_monitors: 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_performance_monitors 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_performance_monitors 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_performance_monitors. 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_performance_monitors 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