remove_array_element

Remove array element at specific index

SERVERCocos SOURCEcaravanglory/cocos-mcp-server

Medium RISK CLASS

Category Write

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/remove-array-element.md

WHAT IT DOES

What remove_array_element does on Cocos

AI agents use remove_array_element to create or update resources in Cocos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cocos environment.

RISK

Why remove_array_element is rated Medium

Removing an array element modifies data (the array loses an element), which is a reversible write operation in the context of an editor with undo support (the server has begin_undo_recording/cancel_undo_recording tools). It's not fully destructive since undo functionality appears available. Severity is medium as misuse could corrupt scene/component data.

From the tool's definition Remove array element at specific index

Attacks that exploit this kind of access

RECOMMENDED RULE

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

remove_array_element Rate-limited

remove_array_element stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "remove_array_element": {
      "limits": [
        {
          "counter": "remove_array_element_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about remove_array_element

What does the remove_array_element tool do? +

Remove array element at specific index. It is categorised as a Write tool in the Cocos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on remove_array_element? +

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

remove_array_element is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit remove_array_element? +

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

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

remove_array_element 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

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →