Critical Risk →

removeEntity

移除单个实体(通过 entityId)

Part of the Cesium Mcp Runtime server.

removeEntity can permanently delete data in Cesium Mcp Runtime, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE CESIUM MCP RUNTIME →

Free to start. No card required.

AI agents may call removeEntity to permanently remove or destroy resources in Cesium Mcp Runtime. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call removeEntity in a loop, permanently destroying resources in Cesium Mcp Runtime. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "removeEntity"
  ]
}

See the full Cesium Mcp Runtime policy for all 43 tools.

Get this rule live on your own Cesium Mcp Runtime server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CESIUM MCP RUNTIME →

View all 43 tools →

These attack patterns abuse exactly the kind of access removeEntity gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so removeEntity only ever does what you allow.

SECURE CESIUM MCP RUNTIME →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the removeEntity tool do? +

移除单个实体(通过 entityId). It is categorised as a Destructive tool in the Cesium Mcp Runtime MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on removeEntity? +

Register the Cesium Mcp Runtime MCP server in PolicyLayer and add a rule for removeEntity: 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 Cesium Mcp Runtime. Nothing to install.

What risk level is removeEntity? +

removeEntity is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit removeEntity? +

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

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

removeEntity is provided by the Cesium Mcp Runtime MCP server (gaopengbin/cesium-mcp-runtime). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Cesium Mcp Runtime tool call.

Deterministic rules across all 43 Cesium Mcp Runtime tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.