Skip to content
Back to skills

Mesh Policy Enforcer

ASecurity

Enforce trust, routing, and tool-usage policy in multi-device OpenClaw setups. Use when users need per-device guardrails, sensitive-task pinning, emergency isolation, or policy-driven task placement.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
securityrustnoderails

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add Arry8/openclaw-edge --skill mesh-policy-enforcer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mesh Policy Enforcer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Mesh Policy Enforcer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/arry8-mesh-policy-enforcer/badge)](https://www.skillsdirectory.com/skills/arry8-mesh-policy-enforcer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: mesh-policy-enforcer
description: Enforce trust, routing, and tool-usage policy in multi-device OpenClaw setups. Use when users need per-device guardrails, sensitive-task pinning, emergency isolation, or policy-driven task placement.
---

# Mesh Policy Enforcer

Apply explicit policy controls to multi-device orchestration.

## Define policy profile

Capture policy as simple rules:

- trusted devices list
- disallowed devices for sensitive tasks
- allowed tools per device class
- escalation targets for policy violations

## Policy checks before execution

Before dispatching a task, verify:

1. destination device trust level
2. task sensitivity label
3. required tools allowed on destination
4. channel/session exposure constraints

If any check fails, block dispatch and report the reason.

## Sensitive-task pinning

Pin high-sensitivity operations to approved nodes only.

Examples:

- credentials/secrets operations
- finance/payment actions
- external messaging actions

## Emergency isolation

When a node is suspicious/unhealthy:

1. stop routing new tasks to it
2. revoke or rotate related access if applicable
3. route pending work to fallback nodes
4. notify user with impact summary

## Audit output

For each blocked/rerouted task, record:

- policy rule triggered
- original destination
- final action (blocked/rerouted)
- user-visible next step

## Guardrails

- Favor deny-by-default for unknown devices.
- Do not silently downgrade policy strictness.
- Require explicit approval for permanent policy changes.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…