Try-It Through MCP

With Try-It enabled for a token, an AI client can send real requests to your environments. This page explains how to enable it, what the model can and cannot do and which controls limit the risk.

Warning: This is a potentially dangerous feature. A token with Try-It on lets a model send real requests to live systems using the credentials of an environment, and the answers go to the AI provider. Enable it for test environments first, keep the limits low and prefer tokens with a narrow list of services.

Roles: Everything on this page is configured by an admin. It needs the mcp_tryit license feature (Business and Unlimited tiers) in addition to mcp. See License and Tiers.

What the model can do#

The model gets two extra tools, list_environments and send_request:

  • list_environments returns the name, id, base URL, the headers every request carries (with sensitive values shown as ********), timeouts and TLS setting of the environments opened to MCP.
  • send_request takes slug, environment_id, method, path (as list_endpoints shows it), path_params, query and body. It works for OpenAPI services only.

The model cannot choose the host or any header. Only a documented operation with its path parameters, query and body can be sent. The URL and every header come from the environment. Binary bodies and Set-Cookie are not returned, the response is cut to the token's size limit, and the environment's sensitive values are masked in what comes back.

Credentials that the API itself returns, for example an access token in a login response, are shown to the model. Whether that is acceptable is the decision of whoever enables the feature. A redirect from the target is followed, so the environment's headers could reach another host the target redirects to.

Enabling it, step by step#

  1. License. Your license must include mcp_tryit.
  2. Environment. On the service page, edit an environment and switch on Available through the MCP server. It must be public. Mark secret headers as Sensitive. See Environments.
  3. Endpoints (optional). On the service's structure page, restrict which endpoints may be called (see below).
  4. Token. On the MCP Server page, edit a token: switch on its Try-It tools and choose the services it may send requests to (a subset of its allowed services).

If anyone other than an administrator later changes an MCP-enabled environment's base URL, TLS setting or headers, the flag switches off until an administrator confirms it.

Choosing allowed endpoints#

By default MCP Try-It: all endpoints allows every documented endpoint. To restrict it, open the service's Service structure page as an administrator:

  • Select endpoints, tags or folders and click Allow in MCP. The change is saved at once and switches the service to only marked.
  • Remove from MCP takes the selected ones out again. It appears when the selection includes an allowed endpoint.
  • Only MCP endpoints shows just the allowed endpoints with the folders and tags leading to them.
  • The mode button switches back to all endpoints after a confirmation. Removing the last mark leaves nothing allowed.
  • An orange warning icon marks every allowed endpoint and every tag or folder that contains one.

Marks are stored per endpoint, so a new endpoint that appears later in a marked tag is not allowed automatically.

Token limits#

Each token sets:

Setting Default Range
Response size handed to the model (KB) 256 1–4096
Requests per minute 30 1–600
Simultaneous requests 2 1–10

Requests are also charged to the mcp_tryit_requests license quota.

Audit#

Every request and every refusal is written to the audit log (mcp_tryit_request, mcp_tryit_rejected) with token name, service, environment, method, path and status. Header values, query values and bodies are never logged. Changing the endpoint selection is audited as mcp_tryit_selection_saved.

Next steps#

Screenshots

Last updated: