# MCP Tool Permission Matrix Builder (`junipr/mcp-tool-permission-matrix-builder`) Actor

Build a permission matrix mapping MCP tools to scopes, auth requirements, data access categories, write/destructive capabilities, risk levels, and review recommendations.

- **URL**: https://apify.com/junipr/mcp-tool-permission-matrix-builder.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.50 / 1,000 schema validateds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## MCP Tool Permission Matrix Builder

### Store Positioning

**Store title:** MCP Tool Permission Matrix Builder

**Short description:** Build a permission matrix mapping MCP tools to scopes, auth requirements, data access categories, write/destructive capabilities, risk levels, and review recommendations.

**SEO title:** MCP Tool Permission Matrix Builder — API, schema, and developer QA

**SEO description:** Build a permission matrix mapping MCP tools to scopes, auth requirements, data access categories, write/destructive capabilities, risk levels, and review recommendations. Use it to catch contract drift, schema mistakes, unsafe endpoint assumptions, and developer-tool quality issues before release.

**Categories:** DEVELOPER\_TOOLS

**Keywords:** mcp, tool, permission, matrix, builder, data qa, api/developer qa

### Pay-Per-Event Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

- Tier: A1 — API/developer QA
- Primary event: `schema-validated` at $0.00650 base
- Default max charge: $10.00
- Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

- `actor-start`: base $0.00500, GOLD $0.00400. MCP Tool Permission Matrix Builder: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `schema-validated`: base $0.00650, GOLD $0.00520. MCP Tool Permission Matrix Builder: charged when schema validated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `contract-rule-checked`: base $0.00390, GOLD $0.00312. MCP Tool Permission Matrix Builder: charged when contract rule checked is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `report-generated`: base $0.05000, GOLD $0.04000. MCP Tool Permission Matrix Builder: charged when report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

### Public Task Concepts

- Build an MCP Tool Permission Matrix stakeholder brief from source rows
- Prioritize MCP Tool Permission Matrix findings with evidence and confidence
- Summarize MCP Tool Permission Matrix metrics into recommended actions
- Prepare an MCP Tool Permission Matrix source table with uncertainty notes
- Export MCP Tool Permission Matrix decision rows for review

Build a permission and risk matrix for MCP tools from supplied manifests, tool definitions, OpenAPI fragments, function specs, docs text, known scopes, and custom risk rules. Use it before exposing an MCP server to agents so each tool has explicit read/write behavior, required scopes, side effects, data category, and confirmation recommendations.

### Inputs

Provide `toolManifests`, `toolDefinitions`, `serverDocs`, `openApiFragments`, `functionSpecs`, `knownScopes`, `riskRules`, `dataCategoryRules`, `includeEvidence`, `strictMode`, `maxTools`, and `timeoutMs`. Defaults are intentionally small so a first run creates a reviewable matrix without scanning a large connector library.

### Output

Rows include `serverName`, `toolName`, `toolDescription`, `permissionName`, `scope`, `scopeRequired`, `actionType`, `resourceType`, `dataCategory`, `readAccess`, `writeAccess`, `destructiveCapability`, `externalSideEffect`, `confirmationRecommended`, `riskLevel`, `evidenceText`, and `warning`. KVS reports summarize high-risk tools, missing scopes, and permission coverage.

### Public source provenance

Tool names and capabilities are derived from the public GitHub MCP server at https://github.com/github/github-mcp-server. The contents:read/write labels are explicit normalized review categories, not a claim that GitHub publishes those exact OAuth scope strings.

### Billing safety

The actor charges `actor-start` before analysis, charges the primary PPE event before each dataset row, and charges the report event before writing report artifacts. `maxChargeUsd` stops work or output gracefully before the configured cap is exceeded.

# Actor input Schema

## `toolManifests` (type: `array`):

Tool Manifests controls MCP Tool Permission Matrix Builder processing for the supplied inputs; keep values conservative for first runs.

## `toolDefinitions` (type: `array`):

Tool Definitions controls MCP Tool Permission Matrix Builder processing for the supplied inputs; keep values conservative for first runs.

## `serverDocs` (type: `array`):

Server Docs controls MCP Tool Permission Matrix Builder processing for the supplied inputs; keep values conservative for first runs.

## `openApiFragments` (type: `array`):

Open API Fragments controls MCP Tool Permission Matrix Builder processing for the supplied inputs; keep values conservative for first runs.

## `functionSpecs` (type: `array`):

Function Specs controls MCP Tool Permission Matrix Builder processing for the supplied inputs; keep values conservative for first runs.

## `knownScopes` (type: `array`):

Known Scopes controls MCP Tool Permission Matrix Builder processing for the supplied inputs; keep values conservative for first runs.

## `riskRules` (type: `array`):

Rules used by MCP Tool Permission Matrix Builder to classify findings and recommendations.

## `dataCategoryRules` (type: `array`):

Rules used by MCP Tool Permission Matrix Builder to classify findings and recommendations.

## `includeEvidence` (type: `boolean`):

Include evidence in output rows or reports when available.

## `strictMode` (type: `boolean`):

Strict Mode controlling how MCP Tool Permission Matrix Builder processes the supplied inputs.

## `maxTools` (type: `number`):

Maximum tools to process in one run; keep defaults low for safe first runs.

## `timeoutMs` (type: `number`):

Maximum time in milliseconds allowed for the MCP Tool Permission Matrix Builder operation before it is treated as timed out.

## `maxChargeUsd` (type: `number`):

Maximum estimated PPE charge allowed for the run before the actor stops gracefully.

## Actor input object example

```json
{
  "toolManifests": [
    {
      "sourceUrl": "https://github.com/github/github-mcp-server",
      "serverName": "github-mcp-server",
      "name": "get_file_contents",
      "permissions": [
        {
          "name": "contents_read",
          "scope": "contents:read",
          "required": true
        }
      ]
    },
    {
      "sourceUrl": "https://github.com/github/github-mcp-server",
      "serverName": "github-mcp-server",
      "name": "create_or_update_file",
      "permissions": [
        {
          "name": "contents_write",
          "scope": "contents:write",
          "required": true
        }
      ]
    },
    {
      "sourceUrl": "https://github.com/github/github-mcp-server",
      "serverName": "github-mcp-server",
      "name": "delete_file",
      "permissions": [
        {
          "name": "contents_write",
          "scope": "contents:write",
          "required": true
        }
      ]
    }
  ],
  "toolDefinitions": [],
  "serverDocs": [],
  "openApiFragments": [],
  "functionSpecs": [],
  "knownScopes": [
    "contents:read",
    "contents:write"
  ],
  "riskRules": [],
  "dataCategoryRules": [],
  "includeEvidence": true,
  "strictMode": true,
  "maxTools": 3,
  "timeoutMs": 5000,
  "maxChargeUsd": 1
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("junipr/mcp-tool-permission-matrix-builder").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("junipr/mcp-tool-permission-matrix-builder").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call junipr/mcp-tool-permission-matrix-builder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/mcp-tool-permission-matrix-builder"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/snrFHC55UHT5hkkkw/builds/gMiPcxrr30dCcPf2H/openapi.json