get_build_settings

Get build settings - shows current limitations

SERVERCocos SOURCEcaravanglory/cocos-mcp-server

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/caravanglory-cocos-mcp-server/get-build-settings.md

WHAT IT DOES

What get_build_settings does on Cocos

AI agents call get_build_settings to retrieve information from Cocos 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_build_settings is rated Low

This tool retrieves and displays build settings information from the Cocos Creator editor. It performs a read-only query operation that returns current configuration state. No data is modified, deleted, or executed. The blast radius of misuse is minimal—an attacker could only learn about build settings, which is informational data. This clearly fits the 'Read' category.

From the tool's definition Tool name is 'get_build_settings' and description states 'shows current limitations', indicating it retrieves or queries build configuration data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_build_settings safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Cocos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_build_settings, this is the rule to start with:

get_build_settings Allowed

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

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

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

FAQ

Questions about get_build_settings

What does the get_build_settings tool do? +

Get build settings - shows current limitations. It is categorised as a Read tool in the Cocos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_build_settings? +

Register the Cocos MCP server in PolicyLayer and add a rule for get_build_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 Cocos. Nothing to install.

What risk level is get_build_settings? +

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

Can I rate-limit get_build_settings? +

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

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

get_build_settings is provided by the Cocos MCP server (caravanglory/cocos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cocos, and thousands of servers like it.

This server

All 157 Cocos 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 →