Tools & execution
What the MCP server exposes, how risky tools are marked, and how calls actually run.
Your MCP server exposes your capabilities as tools, with clear risk markers — and runs them carefully.
What’s exposed
Each non-internal capability becomes a tool, named by its capability id, with its inputs described. Tools a user lacks the permissions for are hidden. Descriptions carry clear risk markers:
- Requires step-up — the action needs re-authentication, which is completed in the widget.
- Destructive — blocked unless you’ve explicitly allowed it.
- Live data — the tool reads or writes real data, not a sandbox.
- A built-in docs-search tool also lets clients search your connected knowledge.
How calls run
How a tool call executes depends on whether you’ve enabled server-side execution.
Bring your own MCP server
If your workspace already runs its own MCP server, you can register it (from the dashboard or the CLI) and Syncanix will forward tool calls to it — optionally acting as the end user.