Toolstile FAQ

Short answers about connections, workspace access, shared accounts, activity records and usage limits. Each one links to the page with the full detail.

What does Toolstile do?

Toolstile is a managed MCP gateway between your agents and remote MCP servers. You connect servers to a workspace once, point each agent at one gateway endpoint, and choose which tools, resources and prompts each agent may use. For the category explanation, see what an MCP gateway does.

Does Toolstile host my MCP servers?

No. Toolstile connects to servers running elsewhere. The managed service requires public HTTPS endpoints on port 443; it cannot reach localhost, private-network servers or servers launched as local processes. Read the connection requirements.

Can I use the same authorization for personal and team work?

No. Each agent authorization belongs to one workspace. Personal and team catalogs are separate. Use the client setup guide to configure separately labeled gateway connections when you need both contexts.

Does adding a connection give every agent access?

No. Grant access to each agent individually. You can grant full access, choose specific tools, resources and prompts, or leave the agent without access to that connection. Read the permission rules.

What happens if a grant and a block conflict?

The explicit block wins, including when a reusable policy grants access. A blocked capability is filtered from discovery and cannot be used through the gateway. Toolstile permissions also remain subject to the connected account's upstream permissions. See how permissions combine.

Does full access include new tools?

Yes. Full access includes supported tools, resources and prompts the server adds later, unless explicitly blocked. Use selected grants when you want to approve capabilities individually.

How do shared accounts work?

In a team workspace, members contribute their own accounts to a shared MCP entry and an administrator approves them. The administrator sets a workspace default, and each member can choose a preferred approved account instead. Agents still need their own access grants, and the dashboard does not show the stored credentials to other members. Read the shared accounts guide.

Will Toolstile switch accounts if my selected account stops working?

No. It does not automatically fall back to another account. Reconnect the selected account or deliberately choose an available approved account using account selection. An unavailable account may disappear from discovery until it becomes usable again.

What happens to an account when its contributor leaves?

An untransferred account becomes unavailable to the team. An explicit handoff can preserve the shared account under another member's control. The contributor's personal connection stays theirs. Read the shared-account handoff guide.

Can I revoke a whole device?

Yes. You can revoke your device and remove its agents' authorizations across workspaces. Team administrators can revoke agent authorizations within their workspace; they cannot globally revoke another person's device. See devices and revocation.

Does Toolstile store full request contents?

Activity records metadata by default; optional debug capture stores arguments and results for selected agents and connections. Capture is off by default and stops after one hour unless extended; only you can start or view personal captures, while team capture is restricted to owners and admins. Captured contents expire after up to 24 hours; activity metadata is retained for 30 days. Upstream errors and diagnostics may contain service-supplied information, and billing/admin retention is separate; see the privacy policy.

Is there a free plan?

Yes. Your personal workspace starts on Free with 5,000 operations per calendar month, and you can also have one Free team workspace. Free allowances reset at 00:00 UTC on the first day of the month. Paid plans start at $29 per workspace per month and offer a seven-day trial for eligible users and workspaces; see pricing.

Does one tool call always equal one operation?

No. One client action can produce several counted requests: discovery pages, requests to several servers, and requests that fail upstream all count. A gateway retry of the same request counts once, but a request your client sends again counts as new. Automatic background maintenance does not count. Forwarding stops at the workspace allowance, with no paid overages. See how operations are counted.

Why might a request be denied when I still have operations left?

An allowance is only one requirement. Workspace membership, agent authorization, permissions, account availability and subscription status can also prevent forwarding. Check the connection and access settings for the selected workspace, then use the troubleshooting guide.

How do I report a security issue?

Use GitHub private vulnerability reporting, as described on the security page. Do not put vulnerability details in a public issue. For account or privacy requests, email support.

How do I get started?

Create an account, connect a public HTTPS MCP server, authorize an agent for your workspace, and grant its access. Follow the getting started guide for the steps.

Need help with an account or a billing question? Email support@toolstile.com.