track_object_creation
Track object creation for a specific class over a duration. Records a baseline count; poll get_object_count afterward to see changes.
This record as markdown: /tools/keeveeg-godot-mcp/track-object-creation.md
What track_object_creation does on Godot
AI agents use track_object_creation to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
duration | number | — | Tracking duration in seconds (default: 10) |
class_name | string | Yes | Godot class name to track (e.g. 'Node2D', 'RigidBody3D') |
Parameters from the server's own tool schema.
Why track_object_creation is rated Medium
An AI agent can call track_object_creation faster than any human can review: one bad instruction and it creates or modifies resources in Godot by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs track_object_creation 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 track_object_creation, this is the rule to start with:
track_object_creation stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 track_object_creation call is checked against it from then on.
Questions about track_object_creation
Track object creation for a specific class over a duration. Records a baseline count; poll get_object_count afterward to see changes. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
track_object_creation accepts 2 parameters: duration, class_name. Required: 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 track_object_creation: 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.
track_object_creation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the track_object_creation 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 track_object_creation. 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.
track_object_creation 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