Get detailed metadata about a specific asset: type, size, UID, and import settings.
AI agents call get_asset_info to retrieve information from Godot Mcp Pilot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about game assets without modifying, deleting, or executing any code. It has no side effects and poses minimal risk even if an AI agent queries unexpected assets. The worst-case scenario is information disclosure, which is low severity in a game development context.
From the tool's definition Tool description states it 'Get[s] detailed metadata about a specific asset: type, size, UID, and import settings.' The verb 'Get' and the focus on retrieving metadata with no mention of modification, deletion, or execution indicates a read-only operation.
Attacks that exploit this kind of access
Get detailed metadata about a specific asset: type, size, UID, and import settings. It is categorised as a Read tool in the Godot Mcp Pilot MCP Server, which means it retrieves data without modifying state.
Register the Godot Mcp Pilot MCP server in PolicyLayer and add a rule for get_asset_info: 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 Mcp Pilot. Nothing to install.
get_asset_info 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_asset_info 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_asset_info. 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_asset_info is provided by the Godot Mcp Pilot MCP server (pushks18/godot-mcp-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →