admin/isphere-ai-bridge
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: trim safety constraints from mcp roadmap

Browse Source
This commit is contained in:
zhaoyilun
2026-07-09 22:02:26 +08:00
parent cfc7787cdd
commit e993ce15fb
8 changed files with 172 additions and 262 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@@ -1,14 +1,13 @@
# iSphere AI Bridge
This project is for building MCP core communication tools for iSphere / IMPlatformClient so AI digital employees can safely use authorized contacts, groups, messages, and files.
This project is for building MCP core communication tools for iSphere / IMPlatformClient so AI digital employees can use contacts, groups, messages, and files through a clear tool surface.
The business goal is not a selector/report project. The business goal is an MCP tool surface for searching contacts, searching groups, receiving/reading messages, sending messages after approval, receiving/downloading files, and sending files after approval.
The business goal is not a selector/report project. The business goal is an MCP tool surface for searching contacts, searching groups, receiving/reading messages, sending messages, receiving/downloading files, and sending files.
## Scope
- Authorized company communication software only.
- Implement read-only MCP tools first: search contacts, search groups, receive/read messages, and receive/download files.
- Keep real sending and file upload behind explicit human approval, audit, and `dry_run` preview.
- Implement the six core MCP capabilities: search contacts, search groups, receive/read messages, send messages, receive/download files, and send files.
- Build from stable capability sources first, then fill gaps with UI automation only where it directly serves a core tool.
- Prefer stable entry points in this order:
1. Existing bridge / API / local service.
2. Local data/log/cache discovery in read-only mode.
@@ -31,10 +30,7 @@ The business goal is not a selector/report project. The business goal is an MCP
- `runs/` - run logs and temporary investigation outputs; ignored by Git except `.gitkeep`.
- `cmd/`, `internal/`, `native/` - current Go MCP server, helper client, tool registration, and C# WinHelper code.
## Safety Baseline
## Operating Notes
- Do not bypass login, licensing, MFA, access control, TLS protections, or endpoint security.
- Do not read non-authorized account data.
- Do not send real messages without explicit human approval.
- Do not modify production databases, logs, config files, registry keys, or binaries during discovery.
- Redact secrets, tokens, private message content, and personal data in reports.
- `runs/` and `evidence/` are local evidence/work directories and are not part of normal commits.
- Route work through the MCP core tool contract instead of expanding selector/report-only nodes.