Protocol and knowledge are different layers
A protocol can describe how to discover resources, read context or invoke tools. That helps interoperability, but it does not by itself define a datum's semantics, who may access it, under which identity, when it expires or what authority it has. A tool response still needs provenance, scope and limits to be interpretable. Memory also requires temporal preservation, dependency control and policies for revalidating information.
Every invocation needs an authority boundary
Before exposing information or performing an action, an application should check identity, tenant, client, observation focus and permissions. A natural-language description may help select a tool, but should not create permission or modify canonical facts. It helps to separate read-only operations from actions with effects and show the person what was queried or requested. An authorization failure should close the operation rather than fall back to a broader search.
An integration must demonstrate its guarantees
To evaluate a specific MCP server or client, inspect the resources it exposes, each tool's schema, error handling, authentication, scope isolation, call logging, freshness and retention policy. The protocol alone does not demonstrate these controls. In AXIGNAL, boundaries between observation, representation, judgment and evidence admission remain necessary even if a future surface uses tool interoperability.
Check how missing data is handled
An integration should also define its behavior for unavailable sources, partial responses, stale content and authorization failures. If a call returns less information, the client should not silently fill gaps or broaden scope. Recording versions and invocations helps review what happened. These are evaluation questions for any MCP connection, not guarantees attributed to an AXIGNAL integration.
Conceptual example
Hypothetical example: an AI client requests a public organization record and its observation date through a tool. A well-scoped server returns only what is authorized and preserves the source and time; the client should not reinterpret that date as proof that the record is current today. This does not claim that AXIGNAL exposes this tool.
Scope and limits
MCP does not certify source quality, grant data access, automatically manage permissions across clients or turn a model output into admitted evidence. Security and compatibility details depend on client and server versions and configuration. Any claim about actual AXIGNAL support requires a verifiable implementation and test.
Editorial basis
This page explains product doctrine and boundaries. It does not demonstrate source coverage or observed outcomes.
Read the product modelExplore Knowledge
Explore AXIGNAL