# validate_cubism_export

A read tool on the Live2D Automation MCP Server MCP server.

Agent View of the PolicyLayer registry record for `validate_cubism_export`. HTML page: https://policylayer.com/tools/j621111-live2d-automation/validate-cubism-export

## Facts

- Tool: `validate_cubism_export`
- Server: Live2D Automation MCP Server (`j621111/live2d-automation`) — https://policylayer.com/tools/j621111-live2d-automation.md
- Homepage: https://github.com/J621111/live2d-automation
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "validate_cubism_export",
    "arguments": {}
  }
}
```

## Why validate_cubism_export is rated Low

The name suggests a validation/checking operation, which is typically read-only (verifying data without modifying it). However, the description is empty, lowering confidence. In context of a Live2D pipeline server, 'validate' most likely checks/reads export data rather than modifying it. Severity is low as validation tools generally have minimal blast radius.

From the tool's own definition: "Tool name 'validate_cubism_export' — no description provided."

## Use case

AI agents call validate_cubism_export to retrieve information from Live2D Automation MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Live2D Automation MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "validate_cubism_export": {}
  }
}
```

## Other tools on Live2D Automation MCP Server (16)

- `execute_cubism_dispatch` — Execute — https://policylayer.com/tools/j621111-live2d-automation/execute-cubism-dispatch.md
- `full_pipeline` — Execute — https://policylayer.com/tools/j621111-live2d-automation/full-pipeline.md
- `resume_cubism_dispatch` — Execute — https://policylayer.com/tools/j621111-live2d-automation/resume-cubism-dispatch.md
- `analyze_parts_with_ai` — Other — https://policylayer.com/tools/j621111-live2d-automation/analyze-parts-with-ai.md
- `build_cubism_psd` — Other — https://policylayer.com/tools/j621111-live2d-automation/build-cubism-psd.md
- `close_session` — Other — https://policylayer.com/tools/j621111-live2d-automation/close-session.md
- `generate_layers` — Other — https://policylayer.com/tools/j621111-live2d-automation/generate-layers.md
- `prepare_cubism_automation` — Other — https://policylayer.com/tools/j621111-live2d-automation/prepare-cubism-automation.md
- `segment_detected_parts` — Other — https://policylayer.com/tools/j621111-live2d-automation/segment-detected-parts.md
- `setup_rigging` — Other — https://policylayer.com/tools/j621111-live2d-automation/setup-rigging.md
- `analyze_photo` — Read — https://policylayer.com/tools/j621111-live2d-automation/analyze-photo.md
- `detect_face_features` — Read — https://policylayer.com/tools/j621111-live2d-automation/detect-face-features.md
- `configure_physics` — Write — https://policylayer.com/tools/j621111-live2d-automation/configure-physics.md
- `create_mesh` — Write — https://policylayer.com/tools/j621111-live2d-automation/create-mesh.md
- `export_model` — Write — https://policylayer.com/tools/j621111-live2d-automation/export-model.md
- `generate_motions` — Write — https://policylayer.com/tools/j621111-live2d-automation/generate-motions.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=j621111-live2d-automation · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/j621111-live2d-automation