# tool-quality-audit

Read-only catalog self-audit for tool titles, descriptions, input documentation, schema examples/defaults/constraints, AI data-flow contracts, prerequisites, capability requirements, mutation side effects, verification paths, and recovery guidance. It evaluates the same centrally compiled metadata exposed to MCP clients, so every current and future tool can be checked against one measurable standard. Filter by exact name/category or return only entries below a score threshold; no Roblox client is required.

Agent View of the PolicyLayer registry record for `tool-quality-audit`. HTML page: https://policylayer.com/tools/executor-mcp-roblox/tool-quality-audit

## Facts

- Tool: `tool-quality-audit`
- Server: Executor Mcp Roblox (`okenjioxx/executor-mcp-roblox`) — https://policylayer.com/tools/executor-mcp-roblox.md
- Homepage: https://github.com/okenjioxx/executor-mcp-roblox
- 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": "tool-quality-audit",
    "arguments": {}
  }
}
```

## Why tool-quality-audit is rated Low

Even though tool-quality-audit only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents call tool-quality-audit to retrieve information from Executor Mcp Roblox 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 Executor Mcp Roblox:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "tool-quality-audit": {}
  }
}
```

## Other tools on Executor Mcp Roblox (290)

- `clear-queue-on-teleport` — Destructive — https://policylayer.com/tools/executor-mcp-roblox/clear-queue-on-teleport.md
- `clear-remote-spy-logs` — Destructive — https://policylayer.com/tools/executor-mcp-roblox/clear-remote-spy-logs.md
- `clear-selection` — Destructive — https://policylayer.com/tools/executor-mcp-roblox/clear-selection.md
- `clear-semantic-index` — Destructive — https://policylayer.com/tools/executor-mcp-roblox/clear-semantic-index.md
- `delete-file` — Destructive — https://policylayer.com/tools/executor-mcp-roblox/delete-file.md
- `delete-folder` — Destructive — https://policylayer.com/tools/executor-mcp-roblox/delete-folder.md
- `destroy-instance` — Destructive — https://policylayer.com/tools/executor-mcp-roblox/destroy-instance.md
- `draw-clear` — Destructive — https://policylayer.com/tools/executor-mcp-roblox/draw-clear.md
- `draw-remove` — Destructive — https://policylayer.com/tools/executor-mcp-roblox/draw-remove.md
- `playbook-delete` — Destructive — https://policylayer.com/tools/executor-mcp-roblox/playbook-delete.md
- `release-closure-reference` — Destructive — https://policylayer.com/tools/executor-mcp-roblox/release-closure-reference.md
- `remote-spy` — Destructive — https://policylayer.com/tools/executor-mcp-roblox/remote-spy.md
- `teach-mode` — Destructive — https://policylayer.com/tools/executor-mcp-roblox/teach-mode.md
- `vm-reset` — Destructive — https://policylayer.com/tools/executor-mcp-roblox/vm-reset.md
- `agent-run` — Execute — https://policylayer.com/tools/executor-mcp-roblox/agent-run.md
- `batch-execute` — Execute — https://policylayer.com/tools/executor-mcp-roblox/batch-execute.md
- `build-call-graph` — Execute — https://policylayer.com/tools/executor-mcp-roblox/build-call-graph.md
- `ensure-remote-spy` — Execute — https://policylayer.com/tools/executor-mcp-roblox/ensure-remote-spy.md
- `execute` — Execute — https://policylayer.com/tools/executor-mcp-roblox/execute.md
- `execute-and-wait` — Execute — https://policylayer.com/tools/executor-mcp-roblox/execute-and-wait.md
- `execute-file` — Execute — https://policylayer.com/tools/executor-mcp-roblox/execute-file.md
- `execute-lua-state` — Execute — https://policylayer.com/tools/executor-mcp-roblox/execute-lua-state.md
- `filter-gc` — Execute — https://policylayer.com/tools/executor-mcp-roblox/filter-gc.md
- `fire-proximity-prompt` — Execute — https://policylayer.com/tools/executor-mcp-roblox/fire-proximity-prompt.md
- `invoke-closure` — Execute — https://policylayer.com/tools/executor-mcp-roblox/invoke-closure.md
- `invoke-method` — Execute — https://policylayer.com/tools/executor-mcp-roblox/invoke-method.md
- `new-c-closure` — Execute — https://policylayer.com/tools/executor-mcp-roblox/new-c-closure.md
- `new-l-closure` — Execute — https://policylayer.com/tools/executor-mcp-roblox/new-l-closure.md
- `new-lua-state-proxy` — Execute — https://policylayer.com/tools/executor-mcp-roblox/new-lua-state-proxy.md
- `playbook-run` — Execute — https://policylayer.com/tools/executor-mcp-roblox/playbook-run.md
- …and 260 more: https://policylayer.com/tools/executor-mcp-roblox.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=executor-mcp-roblox · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/executor-mcp-roblox