get_call_stack
Get the current call stack with local variables when the game is paused at a breakpoint
This record as markdown: /tools/keeveeg-godot-mcp/get-call-stack.md
What get_call_stack does on Godot
AI agents call get_call_stack 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.
Why get_call_stack is rated Low
This tool retrieves debugging information (call stack and local variables) without modifying any game state, code, or resources. It is purely observational and used for inspecting the runtime state of a paused game. No data is created, modified, deleted, or executed—only queried. This is a standard debugging read operation with minimal security risk.
From the tool's definition Tool name 'get_call_stack' and description 'Get the current call stack with local variables when the game is paused at a breakpoint' indicate a read-only debugging operation that retrieves call stack and variable state information.
Attacks that exploit this kind of access
The rule that runs get_call_stack 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 get_call_stack, this is the rule to start with:
get_call_stack 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 get_call_stack call is checked against it from then on.
Questions about get_call_stack
Get the current call stack with local variables when the game is paused at a breakpoint. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP server in PolicyLayer and add a rule for get_call_stack: 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.
get_call_stack 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 get_call_stack 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 get_call_stack. 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.
get_call_stack 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