AI agents call node_find to retrieve information from Godot Devtool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves information about existing nodes in a Godot scene. It performs no side effects, creates no data, executes no code, and has no financial implications. The worst misuse would be information disclosure about project structure, which is low severity. Classification as Read is appropriate.
From the tool's definition Tool description explicitly states 'Find nodes in a scene by name, type, or path substring' — a query/search operation with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access node_find gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for node_find:
{
"version": "1",
"default": "deny",
"tools": {
"node_find": {}
}
}node_find is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find nodes in a scene by name, type, or path substring. It is categorised as a Read tool in the Godot Devtool MCP Server, which means it retrieves data without modifying state.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for node_find: 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 Devtool. Nothing to install.
node_find 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 node_find 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 node_find. 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.
node_find is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.