Security and limits | Taurus Developer Hub

Limits

Limit	Value
Page size	20 rows per call by default, up to 100; the assistant asks for the next page
Result size	A result over 80 KiB is refused rather than cut short, so a partial list never reads as complete. Ask for fewer rows, add filters, or ask for a summary
Sign-in	Renewed automatically. By default you sign in again after 8 hours without use, and at least every 24 hours; your organization may set other limits
Write tools	Off unless your administrator enables them, and your sign-in must include the matching capability

Rules the server enforces

These hold whatever is asked; no prompt can change them.

It acts as you

Every call runs with your own Taurus-PROTECT session: your roles, your tenant, and your name in the audit trail.

Capabilities are checked by Taurus-PROTECT

On every operation, not by the assistant. An operation you did not approve is refused.

It never approves or signs

Approvals in Taurus-PROTECT are signed by named people with their own keys, and the MCP server holds no signing key. A request or proposal created through it still needs your organization’s approvals.

Signed data is verified

Governance rules, and the whitelists checked against them, are verified against your SuperAdmins’ signatures before the assistant sees them.

Complete answers or none

Oversized results are refused rather than truncated, and entries that fail verification are reported rather than silently left out.

It stores nothing

The MCP server keeps no copy of your data, and holds sessions in memory only, until they expire.

Security notes

Use your own account. Everyone signs in individually; never share a session or a connector signed in as someone else.
Treat data as untrusted text. Notes, labels and descriptions stored in Taurus-PROTECT reach the assistant as plain text and could contain instructions. Review what the assistant proposes before you confirm a write.
Keep confirmations on for write tools; allow tools to run without asking only for read tools.
Connect only to the URL your administrator gives you, and check that the sign-in page is your Taurus-PROTECT.
Disconnect when you are done with a device. Removing the connector, or claude mcp logout, deletes the stored sign-in.

Your data and your AI provider

Answers from the MCP server become part of your conversation, so your AI provider processes them under your agreement with it. Check that agreement and your organization’s policy before you connect.