Medium Risk

addWall

沿路径添加墙体

High parameter count (10 properties)

Part of the Cesium Mcp Runtime MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use addWall 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.

Without a policy, an AI agent could call addWall 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.

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

gaopengbin-cesium-mcp-runtime.yaml
tools:
  addWall:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

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

Tool Name addWall
Category Write
Risk Level Medium

View all 43 tools →

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

Browse the full MCP Attack Database →

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

What does the addWall 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 addWall? +

Add a rule in your Intercept YAML policy under the tools section for addWall. 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 addWall? +

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

Can I rate-limit addWall? +

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

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

addWall 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

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.