Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

FEAT: MCP (Model Context Protocol) Integration

Aperta
#1,273 6 commenti 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

enhancement needs design not ready yet
Is your feature request related to a problem? Please describe.

When red teaming agentic AI systems, PyRIT currently requires custom integrations for each external tool, data source, or capability. This creates friction when testing systems that use diverse toolsets and limits the ability to dynamically discover and interact with target capabilities during assessments.

TheModel Context Protocol (MCP) by Anthropic provides a standardized interface for LLM-to-tool communication that's rapidly being adopted across the AI ecosystem. Without MCP support, PyRIT cannot natively interact with MCP-enabled targets or leverage the growing ecosystem of MCP servers for red teaming workflows.

Describe the solution you'd like

Add native MCP support to PyRIT, enabling red teaming agents to dynamically discover and use external tools, data sources, and prompt templates via the MCP protocol.

Core Capabilities:

  • Tools: Execute functions (converters, probes, external APIs, target system tools)
  • Resources: Read data (attack datasets, MITRE ATLAS mappings, reconnaissance results)
  • Prompts: Load templates (red team agent prompts, attack strategies)

Proposed Implementation:

The codebase already defines MCP types in MessagePieceType:

MCP_CALL = "mcp_call"
MCP_LIST_TOOLS = "mcp_list_tools"
MCP_APPROVAL_REQUEST = "mcp_approval_request"

These types aren't implemented yet. This proposal would complete that implementation.

Proposed Usage:

from pyrit.mcp import MCPServerConfig, MCPTransport

# Native MCP support in target
target = OpenAIResponseTarget(
    mcp_servers=[
        MCPServerConfig(
            name="converters", 
            transport=MCPTransport.STDIO, 
            command="python", 
            args=["converters_server.py"]
        ),
        MCPServerConfig(
            name="recon", 
            transport=MCPTransport.SSE, 
            url="http://localhost:8080/sse"
        ),
    ]
)

# Target auto-discovers tools, model can call them during conversation

Implementation Phases:

  1. Core MCP client implementation using the MCP Python SDK
  2. Integration with OpenAIResponseTarget
  3. Integration examples with existing agentic security tools as MCP resources/tool
  4. Documentation and notebooks
Additional context

Relationship to Existing Issues:

  • Supersedes #1083
  • Supersedes #1118

References:

Open Questions:

  • Should example MCP servers live in PyRIT core or a separate repository?
  • Which transport should be prioritized first (STDIO vs SSE)?
  • Any security considerations for MCP server sandboxing during red team operations?

I'm happy to start the implementation and can break this into smaller PRs. Would welcome collaboration from anyone interested in this direction.

Lingua principale
Python
Stelle
4.5k
Fork
896
Merge medio
3g 8h
PR unite (30g)
191

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/PyRIT

Tutte le issue di microsoft/PyRIT

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.