Skip to content
ShopNexus Docs
On this page Checks on every call 1/4

The agent reads data only through the server’s MCP server. It serves Streamable HTTP at /mcp on a port of its own (AGENT_MCP_ADDR), off the :8080 port and outside the ingress. It keeps no session: every POST is one request with its own checks.

Checks on every call

  1. Token

    Each call carries Authorization: Bearer <AGENT_MCP_TOKEN>, compared in constant time. A wrong token is 401 before any MCP handling, and the server logs security: agent MCP call refused without the token.

  2. Moderator

    The X-Console-Member header carries the id of the moderator who asked. The server reads the moderator again through ActiveMember on every call, so a moderator disabled between two tool calls gets nothing from the second.

  3. Tool

    A tool is a thin adapter over a module’s Service; no tool reads a table. A refusal reaches the agent as a tool error with its code; any other failure reaches it as internal error and is logged.

On the agent’s side, only tools with readOnlyHint that are on the agent’s tools list reach the model. Each call has a time limit (AGENT_TOOL_TIMEOUT_MS, 20 seconds by default) and is retried up to AGENT_TOOL_ATTEMPTS times on a timeout or a dropped connection.

Tool list

List tools take cursor and limit (1 to 50, 20 by default) and answer {items, next_cursor}.

ToolReadsRecorded read
countCounts by status of accounts, listings, orders, tickets or report cases, since a date or for all timeno
lookupWhich record an id names: an account, a report case, an order, a listing or a ticket, with the tool that reads itno
ticket_getA ticket, its person, its order, the first page of its chat and the person’s other ticketsthe ticket, its person
ticket_messagesA page of a ticket’s chat, newest firstthe ticket
tickets_listThe support queue: open or resolved tickets, with each chat’s last linethe tickets and their persons
tickets_of_accountThe newest 50 tickets an account opened, or on orders it soldthe account and the tickets
account_getStatus, age, whether it has a phone and an email, listings, orders as buyer, how often it was suspendedno
accounts_listThe newest accounts, those suspended now, or the account an id or a phone number namesno
orders_of_accountAn account’s orders as buyer or as sellerno
listings_of_accountA seller’s listings on sale or soldno
console_actionsThe console’s audit log by record, by moderator or all, without IPsno
order_getAn order, its parties, listing, price, status and the carrier’s status nowno
listing_getA listing in any status but deleted, as its seller sees itno
price_guideA listing’s price against the median of listings in the same category and conditionno
report_cases_listThe report queue: open or resolved casesno
report_case_getAn account’s report case: reasons, listings reported, every report with its note, the resolutionthe account, the reports, the reporters

Personal data reads

Each time a tool reads personal data (messages, notes, a ticket’s person, reporters), the server writes a row to console_agent_reads: moderator, tool, the ids and the time. Rows are kept 90 days, and admins see them beside the console’s audit log. The requirement is NFR-PRIV-02.

Text from users

The MCP server’s instructions and the agent’s system prompt both state that text users wrote (messages, notes, listing descriptions) is quoted as data only. The agent has no write tool, so an instruction hidden in that text changes no data.

ShopNexus Docs
EN VI