Critical Risk →

foliage

Foliage painting, types, sampling, and settings. Actions: - list_types: List foliage types in level - get_settings: Read foliage type settings. Params: foliageTypeName - sample: Query instances in region. Params: center, radius, foliageType? - paint: Add foliage. Params: foliageType, center, rad...

High parameter count (14 properties)

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

ue-mcp Destructive Risk 4/5

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

Without a policy, an AI agent could call foliage in a loop, permanently destroying resources in Ue. There is no undo for destructive operations. Intercept 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.

ue.yaml
tools:
  foliage:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Ue policy for all 20 tools.

Tool Name foliage
Category Destructive
MCP Server Ue MCP Server
Risk Level Critical

View all 20 tools →

Agents calling destructive-class tools like foliage 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 Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

foliage is one of the critical-risk operations in Ue. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the foliage tool do? +

Foliage painting, types, sampling, and settings. Actions: - list_types: List foliage types in level - get_settings: Read foliage type settings. Params: foliageTypeName - sample: Query instances in region. Params: center, radius, foliageType? - paint: Add foliage. Params: foliageType, center, radius, count?, density? - erase: Remove foliage. Params: center, radius, foliageType? - create_type: Create foliage type from mesh. Params: meshPath, name?, packagePath? - set_settings: Modify type settings. Params: foliageTypeName, settings. It is categorised as a Destructive tool in the Ue 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 foliage? +

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

What risk level is foliage? +

foliage 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 foliage? +

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

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

foliage is provided by the Ue MCP server (ue-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Ue

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.