get_audio_settings

Get all audio settings including bus layout, default bus, and driver info

SERVERGodot SOURCE@keeveeg/godot-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/keeveeg-godot-mcp/get-audio-settings.md

WHAT IT DOES

What get_audio_settings does on Godot

AI agents call get_audio_settings 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.

RISK

Why get_audio_settings is rated Low

This tool retrieves audio configuration data from a Godot game engine project without side effects. It queries existing state (bus layout, default bus, driver info) and returns information. There is no capability to execute code, modify settings, delete resources, or perform any destructive operations. This is a straightforward data retrieval tool with minimal risk.

From the tool's definition Tool name 'get_audio_settings' and description 'Get all audio settings' indicate a retrieval operation with no modification or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_audio_settings Allowed

get_audio_settings 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": {
    "get_audio_settings": {}
  }
}

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 get_audio_settings call is checked against it from then on.

FAQ

Questions about get_audio_settings

What does the get_audio_settings tool do? +

Get all audio settings including bus layout, default bus, and driver info. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_audio_settings? +

Register the Godot MCP server in PolicyLayer and add a rule for get_audio_settings: 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 get_audio_settings? +

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

Can I rate-limit get_audio_settings? +

Yes. Add a rate_limit block to the get_audio_settings 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 get_audio_settings completely? +

Set action: deny in the PolicyLayer policy for get_audio_settings. 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 get_audio_settings? +

get_audio_settings 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.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 321 Godot tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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