open_preferences_settings
Open preferences settings panel
This record as markdown: /tools/caravanglory-cocos-mcp-server/open-preferences-settings.md
What open_preferences_settings does on Cocos
AI agents invoke open_preferences_settings to trigger actions in Cocos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why open_preferences_settings is rated High
Opening a settings panel triggers a UI operation in the editor — it's not a passive read but an action that causes the editor to display/open a panel. No data is modified or destroyed, but it executes an editor action. Severity is low as it only opens a UI panel with no direct data impact.
From the tool's definition Open preferences settings panel
Attacks that exploit this kind of access
The rule that runs open_preferences_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 open_preferences_settings, this is the rule to start with:
open_preferences_settings stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cocos, apply this rule, and every open_preferences_settings call is checked against it from then on.
Questions about open_preferences_settings
Open preferences settings panel. It is categorised as a Execute tool in the Cocos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cocos MCP server in PolicyLayer and add a rule for open_preferences_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.
open_preferences_settings is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the open_preferences_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.
Set action: deny in the PolicyLayer policy for open_preferences_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.
open_preferences_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.
More on Cocos, and thousands of servers like it.
Across the catalogue