MCP

How it works

MCP exposes external capabilities through a standard protocol. Discovering a tool does not authorize Yasnora or a Group to use it.

Before you start

Use only an MCP server approved for the workspace. Review its owner, transport, requested tools and whether each tool reads data or changes an external system before binding it to an agent.

What to do

1. Have an authorized administrator review the server and capabilities.
2. Identify which actions read data and which modify external state.
3. Approve only required capabilities and explicitly bind them to the Group.
4. Review the target and effect of each requested consequential action.

Verify the result

Even a read-only tool can expose sensitive material. Reject unexpected requests or excessive scopes; keep credentials server-side.

If it does not work

If discovery or a tool call fails, verify server availability, authentication, workspace binding and the exact requested capability. Revoke the binding if the server identity or scope changes. Tool availability never grants a user additional permission.