PipedreamHQ / PipedreamHQ/pipedream

Request: Review auto-generated MCP permission manifest for Pipedream

Open
#18,228 0 comments 0 reactions 0 assignees View on GitHub
tracked internally triaged
Dominant language
JavaScript
Stars
11.7k
Forks
5.8k
Avg merge
3d 10h
Merged PRs (30d)
102

Description

Dear Authors / Maintainers,

We are researchers from the University of St. Gallen studying how to make Model Context Protocol (MCP) servers safer to run via a sandboxed permission system. As part of our study, we auto generated a permission manifest for your MCP server and would love your feedback on whether it is correct and complete.

The MCP server in question is: Pipedream

Please review the manifest below and let us know:

* Are the permissions and their scopes correct?
* Are any permissions missing?
* Do any permissions need to be runtime-scoped (e.g., a specific project directory) rather than global?

**Proposed manifest (please review)**

```json
{
"description": "Pipedream MCP server (reference implementation). Node.js/Express server exposing SSE, Streamable HTTP, and stdio transports to run Pipedream Connect tools. It authenticates to Pipedream via the SDK, optionally uses OpenAI for embeddings/LLM, and Supabase for app discovery. Intended for local/self-hosted development.",
"permissions": [
"mcp.ac.network.server",
"mcp.ac.network.client",
"mcp.ac.system.env.read"
]
}
```

Please let us know if you have any questions and/or remarks.

In case you want to see the (current) full permission system:
MCP Permission System

| Permission | Description | Notes |
| ---------------------------------- | ------------------------------- | ------------------------------------------ |
| `mcp.ac.filesystem.read` | Read files/directories | |
| `mcp.ac.filesystem.write` | Write/create files | |
| `mcp.ac.filesystem.delete` | Delete files or directories | |
| `mcp.ac.system.env.read` | Read environment variables | e.g., `API_KEY`, `PATH` |
| `mcp.ac.system.env.write` | Set environment variables | setting the env variables |
| `mcp.ac.system.exec` | Execute OS commands | CLI runners, shells |
| `mcp.ac.system.process` | List or kill processes | |
| `mcp.ac.network.client` | General Outgoing network access | |
| `mcp.ac.network.server` | Accept incoming connections | |
| `mcp.ac.network.bluetooth` | Use Bluetooth connections | macOS TCC-protected |
| `mcp.ac.peripheral.camera` | Capture images/video | macOS TCC-controlled |
| `mcp.ac.peripheral.microphone` | Record audio | TCC-protected |
| `mcp.ac.peripheral.speaker` | Play audio | |
| `mcp.ac.peripheral.screen.capture` | Screen capture | Requires consent (macOS: Screen Recording) |
| `mcp.ac.location` | Access location data | From Wi-Fi, IP, GNSS |
| `mcp.ac.notifications.post` | Show system notifications | macOS/Windows |
| `mcp.ac.clipboard.read` / `.write` | Read/write clipboard | Copy-paste support |

Thank you very much for your time and your efforts in making MCP more secure.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.