read_marker

List Marker2D/Marker3D position markers across scenes.

SERVERGodot SOURCE@yanhuifair/godot-mcp

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yanhuifair-godot-mcp/read-marker.md

WHAT IT DOES

What read_marker does on Godot

AI agents call read_marker 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
`scene_path`	object	—
`marker_type`	object	—	Marker2D or Marker3D

Parameters from the server's own tool schema.

RISK

Why read_marker is rated Low

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

RECOMMENDED RULE

The rule that runs read_marker 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 read_marker, this is the rule to start with:

read_marker Allowed

read_marker is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "read_marker": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every read_marker call is checked against it from then on.

FAQ

Questions about read_marker

What does the read_marker tool do? +

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.

What parameters does read_marker accept? +

read_marker accepts 2 parameters: scene_path, marker_type. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on read_marker? +

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.

What risk level is read_marker? +

read_marker is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit read_marker? +

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.

How do I block read_marker completely? +

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.

What MCP server provides read_marker? +

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.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 282 Godot tools →

Across the catalogue

read_input_file on 0gzk →claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →