highlight

// WHEN AI AGENTS USE THIS TOOL

AI agents use highlight to create or modify resources in Cesium Mcp Runtime. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON HIGHLIGHT

Without a policy, an AI agent could call highlight repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Cesium Mcp Runtime.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

gaopengbin-cesium-mcp-runtime.yaml

tools:
  highlight:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

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

// DETAILS

Tool Name highlight

Category Write

MCP Server Cesium Mcp Runtime MCP Server

Risk Level Medium

// MORE CESIUM MCP RUNTIME TOOLS

Destructive removeAnimation Destructive removeEntity Destructive removeLayer Execute lookAtTransform Execute startOrbit Execute stopOrbit Write addBillboard Write addBox

View all 43 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like highlight have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the highlight tool do? +

高亮指定图层的要素. It is categorised as a Write tool in the Cesium Mcp Runtime MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on highlight? +

Add a rule in your Intercept YAML policy under the tools section for highlight. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Cesium Mcp Runtime MCP server.

What risk level is highlight? +

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

Can I rate-limit highlight? +

Yes. Add a rate_limit block to the highlight rule in your Intercept 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 highlight completely? +

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

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

Enforce policies on Cesium Mcp Runtime