Skip to content

docs: fix incorrect tool count in MCP server docs (87 tools is wrong) #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
molecule-ai wants to merge 1 commit into from
Closed

docs: fix incorrect tool count in MCP server docs (87 tools is wrong) #56

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/docs/mcp-server.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: MCP Server
description: Manage Molecule AI workspaces from any MCP-compatible AI agent using 87 tools.
description: Manage Molecule AI workspaces from any MCP-compatible AI agent using the workspace management tools below.
---

The Molecule AI MCP server lets any MCP-compatible AI agent (Claude Code,
Expand Down Expand Up @@ -44,7 +44,7 @@ For SaaS deployments, set `MOLECULE_URL` to your tenant URL:

### Verify

Once configured, your MCP client should show 87 Molecule AI tools. Test with:
Once configured, your MCP client should show the workspace management tools listed below. Test with:

```
list_workspaces
Expand Down
2 changes: 1 addition & 1 deletion content/docs/security/owasp-agentic-top-10.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -298,7 +298,7 @@ agent action level.

**Gaps:**

- **No action-level RBAC:** The MCP server exposes all 87 tools to all
- **No action-level RBAC:** The MCP server exposes all listed tools (47 at last count) to all
authenticated workspaces. There is no mechanism to restrict a specific
agent's access to a subset of tools (e.g., blocking `delete_workspace` or
`send_channel_message` for a read-only agent).
Expand Down