query_server_port

Query editor server current port

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/query-server-port.md

WHAT IT DOES

What query_server_port does on Cocos

AI agents call query_server_port 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 query_server_port is rated Low

This tool retrieves configuration information (the current port) from the editor server without modifying, executing, or deleting anything. It is a pure read operation with minimal security impact—knowing the server port is generally non-sensitive metadata. Severity is low because exposing this information poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'query_server_port' and description 'Query editor server current port' indicate a straightforward information retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs query_server_port 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 query_server_port, this is the rule to start with:

query_server_port Allowed

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

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 query_server_port call is checked against it from then on.

FAQ

Questions about query_server_port

What does the query_server_port tool do? +

Query editor server current port. 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 query_server_port? +

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

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

Can I rate-limit query_server_port? +

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

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

query_server_port 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

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →