find_nearby_nodes
🔴 Game must be running. Find nodes within a radius of a world position
This record as markdown: /tools/keeveeg-godot-mcp/find-nearby-nodes.md
What find_nearby_nodes does on Godot
AI agents call find_nearby_nodes 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 |
|---|---|---|---|
radius | number | Yes | Search radius |
position | array | Yes | Position as [x, y, z] |
Parameters from the server's own tool schema.
Why find_nearby_nodes is rated Low
This tool searches for and returns data about nodes in a game world at a given location. It has no side effects: it does not create, modify, delete, or execute any game behavior. The requirement that 'game must be running' indicates it operates on live game state, but the operation itself is read-only.
From the tool's definition find_nearby_nodes: queries/retrieves nodes within a spatial radius; no modification, deletion, or execution of game logic occurs—purely a retrieval operation.
Attacks that exploit this kind of access
The rule that runs find_nearby_nodes 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 find_nearby_nodes, this is the rule to start with:
find_nearby_nodes 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 find_nearby_nodes call is checked against it from then on.
Questions about find_nearby_nodes
🔴 Game must be running. Find nodes within a radius of a world position. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
find_nearby_nodes accepts 2 parameters: radius, position. Required: radius, position. 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 find_nearby_nodes: 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.
find_nearby_nodes 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 find_nearby_nodes 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 find_nearby_nodes. 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.
find_nearby_nodes 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