AI agents call read_marker to retrieve information from Godot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
scene_path | object | — | |
marker_type | object | — | Marker2D or Marker3D |
Parameters from the server's own tool schema.
This tool retrieves metadata about marker positions in a Godot project without creating, modifying, deleting, or executing any side effects. It is a pure read operation on static scene data, making it low severity even in an automated agent context—the worst outcome is information disclosure.
From the tool's definition Tool name 'read_marker' and description 'List Marker2D/Marker3D position markers across scenes' indicate a query/retrieval operation with no modification.
Attacks that exploit this kind of access
List Marker2D/Marker3D position markers across scenes. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
read_marker accepts 2 parameters: scene_path, marker_type. 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 read_marker: 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.
read_marker 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 read_marker 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 read_marker. 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.
read_marker is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
read_marker is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →