Read the project-local godot-devtool safety policy and default enforcement state
AI agents call get_safety_policy 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 tool retrieves and queries configuration data (a safety policy document and its enforcement state) without modifying, executing, or deleting anything. It is a pure read operation with minimal blast radius if misused by an AI agent—the worst outcome would be information disclosure of local policy settings.
From the tool's definition Tool name contains 'get_' prefix and description explicitly states 'Read the project-local godot-devtool safety policy'. The verb 'Read' and the retrieval-only nature indicate no side effects.
Documented attack patterns abuse exactly the kind of access get_safety_policy 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 get_safety_policy:
{
"version": "1",
"default": "deny",
"tools": {
"get_safety_policy": {}
}
}get_safety_policy 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.
Read the project-local godot-devtool safety policy and default enforcement state. 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 get_safety_policy: 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.
get_safety_policy 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_safety_policy 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_safety_policy. 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_safety_policy 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.