MCP, tools and confirmation
Add an MCP server, discover its tools with readable schemas, then allow tools per agent with a visible policy.
Before you start
- An MCP server URL and transport.
- Authentication details, if the server requires them.
Steps
Add the server
Provide URL and transport; connection and execution checks SSRF, DNS and redirects.
Discover tools
Readable schemas; discovery pagination is bounded, and errors are actionable.
Authorize per agent
The tool name is composed of server + tool, so two servers never collide.
Confirm
A sensitive tool shows its policy (allow, deny or confirm) before it runs.
Expected result
The effective tool belongs to the right server, and a DENY/CONFIRM policy is honoured; execution can be resumed.
Errors and solutions
Discovery fails
The URL may be private or unreachable; an internal or localhost endpoint is refused from the shared SaaS.
Tool not found
Check the composed name (server + tool) and the per-agent policy.
Screens
/mcp/[id] — MCP detail: connection, discovered tools, policies, diagnostic.Reference of the console screen to capture (redacted) during the browser recipe (XP14). No fabricated image is shown.
Limits and dependencies
A local Ollama or MCP server is not enabled without controlled connectivity; a client server is never exposed.
Provider documentation
Documentation consulted on 2026-10-11.