MCP Gateway Usage, limits and audit log.

/mcp-gateway/usage-and-audit

Every tool call leaves a metadata record. Each connector has a monthly allowance, and the Portal always shows the limit that applies to you.

[ 02 // the activity log ]
[ 02 ]

Every call leaves a record.
Metadata only.

The log keeps which person, which tool, which AI client, when, how long it took and how it ended. It is the full-history companion to the Dashboard.

What a record holds

The tool, the connector, the MCP client, the team member it is attributed to, timing, and the outcome. A failed call also keeps an error detail of up to 2,000 characters.

What it never holds

The call’s request parameters, and the data a successful call returned. The log shows what ran without exposing the contents of a ticket, asset or device record.

A failure keeps its error text

The error detail can include text from the vendor, and a vendor’s message can name a record or repeat a value. Credential patterns are redacted. Treat log access and exports as sensitive.

Who sees it

Owners, co-owners and administrators browse, filter, sort and export the full window to CSV. A member sees their own most recent 100 calls.

What the Activity log shows

Free
100 calls
your most recent
Pro and Business
Last 90 days
of activity
Enterprise
Full history
of your calls

The window is how far back the page lets you browse. It is not how long records are kept: StackJack keeps usage records for as long as your organization is active.

[ 03 // the monthly allowance ]
[ 03 ]

A volume limit,
per connector.

Each connector subscription includes a monthly allowance of successful tool calls. It is a volume limit. It is not a speed limit.

Successful tool calls per connector, per billing cycle

Free
100
calls per connector, per cycle
Pro
5,000
calls per connector, per cycle
Business
50,000
calls per connector, per cycle
Enterprise
Custom
calls per connector, per cycle

Per connector, not account-wide

HaloPSA on Pro and NinjaOne on Business have 5,000 calls for Halo tools and 50,000 for Ninja tools, tracked on each subscription’s own cycle. All connections of one connector share its allowance.

Only successful calls count

A call that fails, whether StackJack blocked it or the vendor rejected it, is recorded and consumes nothing. StackJack platform tools never count.

What happens at the limit

Calls to that connector return a monthly limit error until the next cycle or an upgrade. The Portal always shows the limit that applies to you, which can differ for an Enterprise arrangement.

Calls are also paced toward each vendor’s API, and a vendor may apply its own limit.

[ 04 // where your data lives ]
[ 04 ]

Two regions.
One vault per region.

Interactive tool calls pass through StackJack. The records above are what stays.

A storage home for each organization

Your storage home decides where StackJack’s regional database, cache, blob storage and key vault are: US (Azure) or EU (Azure Sweden Central). Each region has its own set. It does not make every processor regional.

Credentials stay in a vault

Connector credentials sit in a dedicated secrets vault, encrypted at rest and in transit. They are not in app storage and are not logged.

What the storage home does not cover

AI providers, error monitoring, email and identity services process under their own terms and locations. The External Data Processing page in the docs lists each service and what it receives.

A result too large to send back

If a result is too large to send back to the AI, StackJack saves it to a temporary download link for you, unless the result carries credentials.

[ 05 // faq ]
[ 05 ]

Questions.

Does StackJack store any of my business data?

Not on the gateway path. Interactive tool calls pass through StackJack. The audit log keeps metadata: who called which tool, when, how long it took and how it ended. It does not keep the parameters or the data a successful call returned. A failed call also keeps its error text, which can include text from the vendor. If a result is too large to send back to the AI, StackJack saves it to a temporary download link for you. Automations and AI Governance keep the data their own pages describe. Credentials live in a dedicated secrets vault, encrypted at rest.

Can I run StackJack on my own servers or in my own cloud?

No. StackJack is hosted only: it runs in StackJack’s own Azure regions, US or EU, and there is no edition of it to install on your own servers or in your own cloud. What you can bring is the AI behind Automations, which can run in your own Azure subscription.

Where do I see my usage?

On the Dashboard for the recent glance, under Billing and usage for the Activity log, and on the Billing pages for the meters against each connector’s allowance. Where to see your usage.

[ 07 // start ]

Jack into your stack.

Start free. Every connector includes a free tier that never expires, and every plan includes per-user sign-in.