microsoft/wassette

Implemnet the required security considerations from MCP Spec

Open

#192 opened on Aug 18, 2025

View on GitHub
 (0 comments) (1 reaction) (1 assignee)Rust (64 forks)github user discovery
enhancementhelp wantedquestionsecurity

Repository metrics

Stars
 (913 stars)
PR merge metrics
 (PR metrics pending)

Description

Quote from the spec: https://modelcontextprotocol.io/specification/2025-06-18/server/tools#security-considerations

Servers MUST:

  • Validate all tool inputs
  • Implement proper access controls
  • Rate limit tool invocations
  • Sanitize tool outputs

We need to make sure that Wassette has properly implemented all the security features.

Contributor guide

Research direction
Review the MCP spec section on security, then implement input validation, access controls, rate limiting, and output sanitization in the Wassette runtime. Look for existing patterns in the codebase for handling tool invocations.
Tech stack
rust
Domain
securitybackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustWebAssemblyMCP understanding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65