Skip to main content

Connect Your Agent

This page covers the agent-side wiring for AgentSuite-Red: the request/response contract your agent must implement and the ForgingGround MCP endpoint your agent calls into. Once connected, you'll drive scans from the SaaS console or, for self-hosted setups, from your own on-prem deployment.

Agent contract​

AgentSuite-Red drives your agent through two surfaces:

  1. An HTTP endpoint you host — AgentSuite-Red sends queries here.
  2. The ForgingGround MCP server — your agent calls this to interact with simulated environments.

HTTP endpoint contract​

Expose an endpoint that takes a query and an optional session_id and returns the agent's final response as a string:

def agent_endpoint(query: str, session_id: Optional[str] = None) -> str:
    """
    Args:
        query: The task instruction input for your agent.
        session_id: (Optional) The unique session ID to track multi-turn agent conversation.

    Returns:
        Your agent's final response after processing the query and calling any tools.
    """
    response = your_agent.run(query)
    return response
Multi-turn sessions

session_id is technically optional in the signature, but your endpoint must support it. AgentSuite-Red iteratively sends queries during multi-turn red-teaming; queries with the same session_id must be applied incrementally within a consistent session.

ForgingGround MCP endpoint​

Your agent connects to ForgingGround via a standard Streamable HTTP MCP endpoint:

URL:  https://agentsuite-red.virtueai.cc/forgingground/mcp
Auth: X-API-Key: <your-api-key>

Your API key is provided when you create an account on the AgentSuite-Red platform. Pass it in the X-API-Key header with every MCP request.

With these two surfaces in place, head to Run Red-Teaming Scan to launch your first scan.