get_object_count
Get count of live objects, optionally filtered by class name
This record as markdown: /tools/keeveeg-godot-mcp/get-object-count.md
What get_object_count does on Godot
AI agents call get_object_count 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 |
|---|---|---|---|
class_name | string | — | Filter by class name, or omit for total count |
Parameters from the server's own tool schema.
Why get_object_count is rated Low
This tool queries runtime state (object counts) and returns information. It has no side effects, does not create, modify, or delete data, and does not execute arbitrary code or trigger external operations. It is a straightforward diagnostic/introspection read operation typical of game engine APIs.
From the tool's definition Tool name is 'get_object_count' with description 'Get count of live objects, optionally filtered by class name' — this retrieves a count/metric with no modification of state.
Attacks that exploit this kind of access
The rule that runs get_object_count 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_object_count, this is the rule to start with:
get_object_count 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_object_count call is checked against it from then on.
Questions about get_object_count
Get count of live objects, optionally filtered by class name. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
get_object_count accepts 1 parameter: class_name. 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_object_count: 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_object_count 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_object_count 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_object_count. 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_object_count 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