start_preview_server

A execute tool on the Cocos MCP server.

SERVERCocos SOURCEcaravanglory/cocos-mcp-server
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/caravanglory-cocos-mcp-server/start-preview-server.md

What start_preview_server does on Cocos

AI agents invoke start_preview_server 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 start_preview_server is rated High

Starting a preview server is an Execute category action because it initiates an external process/service whose behavior and side effects depend on the environment and arguments provided. While not immediately destructive or financial, it represents code/process execution.

From the tool's definition The tool 'start_preview_server' starts a preview server, which triggers an external operation (server startup) whose effects depend on system state and configuration. This is an execution action that launches a process.

Questions about start_preview_server

What does the start_preview_server tool do? +

start_preview_server is a execute tool on the Cocos MCP server. 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.

How do I enforce a policy on start_preview_server? +

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

start_preview_server is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_preview_server? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Cocos's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.