Serve the semantic layer over MCP

読了まで約65 分分、7 節 節の 5 例 例。

第2026.11.15版 2026年11月19日時点で例が通過 78 例中 78 例が合格 変更点

AIによる翻訳。英語版は人による検証済みである。 当社の書籍の作り方

英語版の書籍(版2026.11.15)から翻訳した。 原文を読む

この部分はまだ翻訳されていないため、英語で表示している。

By the end of this chapter, you can serve the shop's governed metrics as MCP tools that answer for the role the server was built for, return each answer with its provenance as structured data, test the server in memory, and run the book's agent through it as a host.

The shop's teams ask their questions from the assistant each person already uses, but the agent so far lives inside the book's Python: chapter 6 gave it five metric tools over the semantic layer, and chapter 9 put each role's row filters, column masks and minimum group size underneath them, in lib/policies.py. People in the shop don't work inside that Python. Each assistant, a chat app on a desktop or an editor with an agent built in, could get its own copy of the tools, and then each copy would need its own copy of the access rules, kept in step by hand. The first copy that drifts gives a regional lead another region's revenue.

The Model Context Protocol (MCP) removes the copies. MCP is an open protocol in which an application, the host, runs a client for each server it connects to, and a server offers tools that the host's model can call. Model Context Protocol in Practice covers the protocol, from host, client and server to authorization. Here, the shop's semantic layer becomes one MCP server, which this chapter calls the semantic server, in lib/semantic_server.py. It offers the same five tools as the in-process agent, through chapter 9's PolicyToolbox, the metric tools with the role's access rules underneath, so every host that connects gets the same metrics and the same rules. The examples use the Python software development kit for MCP, mcp 2.3.0, which speaks the specification's revision 2026-07-28, and every one of them runs in memory, with no port and no process.

この部分はまだ翻訳されていないため、英語で表示している。

Turn metrics into tools

最終変更:版2026.11.12

An MCP tool is a name, a description the model reads, a JSON Schema for its arguments and, optionally, a schema for its result. A client discovers a server's tools with tools/list and calls one with tools/call. The specification says the list must not vary per connection, though it may vary with the authorization presented on the request, and that servers should return tools in a deterministic order (tools). So the questions for a semantic layer are which tools to offer, and whether a role should see fewer of them.

We recommend offering the tools the agent already has. Chapter 6 chose five for the shop's agent: list_metrics, describe_metric, query_metric, ask_back and cannot_answer. They were measured on the golden questions, whose answers were checked by running them, and they ask the model to choose a metric request, never to write SQL. build_server() in lib/semantic_server.py registers one MCP tool for each, with a description the model reads and typed arguments, and each tool body calls the same method of chapter 9's PolicyToolbox that the in-process agent calls. The tools are registered in name order. Each is marked read-only, idempotent and closed-world with MCP's tool annotations. Model Context Protocol in Practice explains how to write descriptions the model reads and why annotations are hints, not guarantees.

What a role changes is easiest to see side by side: a server for the analyst, who sees everything, and one for the support team, who may see no revenue. The code lists each server's tools and compares its list_metrics catalog with the one the in-process agent puts in its prompt.

list-metric-tools.py Python 3.12.15 · anyio 4.16.0 · duckdb 2.0.0 · mcp 2.3.0 · pydantic 2.14.3 · pyyaml 6.0.3 · sqlglot 30.31.0 合格
"""The semantic layer as an MCP server: the tools it lists, what query_metric takes, and each role's catalog.The `support, metrics` line settles that support's catalog holds no revenue metric, and the `same catalog as thein-process agent` lines settle that each catalog is the prompt's own text."""import anyiofrom mcp import Clientfrom lib.metric_tools import catalogfrom lib.policies import PolicyLayer, policy_forfrom lib.semantic import loadfrom lib.semantic_server import build_serverfrom lib.warehouse import connectcon, layer = connect(), load()async def main():    listed = {}    for role in ("analyst", "support"):        async with Client(build_server(role, shop=con, layer=layer)) as client:   # in memory: no port, no process            tools = (await client.list_tools()).tools            text = (await client.call_tool("list_metrics", {})).structured_content["text"]        listed[role] = [t.name for t in tools]        metrics = [line[2:].split(":")[0] for line in text.splitlines()]   # catalog lines start with "- ", then the name        print(f"{role}, tools: {', '.join(listed[role])}")        print(f"{role}, metrics in list_metrics: {len(metrics)}")        print(f"{role}, metrics: {', '.join(metrics)}")        in_process = catalog(PolicyLayer(layer, policy_for(role), con))        same = text == in_process                  # PolicyLayer builds the in-process prompt's catalog, so MCP must match it        assert same        print(f"{role}, same catalog as the in-process agent: {'yes' if same else 'no'}")    query = next(t for t in tools if t.name == "query_metric")    print(f"query_metric inputs: {', '.join(query.input_schema['properties'])}")    print(f"query_metric requires: {', '.join(query.input_schema['required'])}")    print(f"tools marked read-only: {sum(t.annotations.read_only_hint for t in tools)} of {len(tools)}")    print(f"tools with a role input: {sum('role' in t.input_schema['properties'] for t in tools)}")    print(f"same tool list for both roles: {listed['analyst'] == listed['support']}")anyio.run(main)
出力python list-metric-tools.py
analyst, tools: ask_back, cannot_answer, describe_metric, list_metrics, query_metric
analyst, metrics in list_metrics: 10
analyst, metrics: net_revenue, gross_revenue, orders, line_net_revenue, units_sold, refunds, order_refunds, new_customers, refund_rate, average_order_value
analyst, same catalog as the in-process agent: yes
support, tools: ask_back, cannot_answer, describe_metric, list_metrics, query_metric
support, metrics in list_metrics: 5
support, metrics: orders, units_sold, refunds, order_refunds, new_customers
support, same catalog as the in-process agent: yes
query_metric inputs: metrics, group_by, filters, order_by, limit
query_metric requires: metrics
tools marked read-only: 5 of 5
tools with a role input: 0
same tool list for both roles: True

Both servers list the same tools: ask_back, cannot_answer, describe_metric, list_metrics, query_metric. What differs is the catalog. The analyst's list_metrics returns 10 metrics and support's 5: orders, units_sold, refunds, order_refunds, new_customers. Every revenue metric is gone from support's catalog, because chapter 9's PolicyLayer hides any metric that reads a column its role is denied. For both roles, the catalog over MCP is the same text the in-process agent puts in its prompt. That matters for the host: an unchanged catalog means an unchanged prompt.

query_metric takes metrics, group_by, filters, order_by, limit and requires only metrics. Of the server's tools, 5 of 5 are marked read-only, and 0 take an argument called role, which is the subject of the next section.

Keeping one tool list for every role was a choice. The specification would allow support's server to list fewer tools, but each of the five tools is useful to every role, and the role changes what a tool returns, not whether it exists. A role that can't use a tool at all is the case for shortening the list, and Model Context Protocol in Practice covers scope tools by what the token allows. The cost of a long list is the subject of the same book's keep the tool list small.

Working rule: Serve the tools your agent was measured with, each one a thin call into the same code the in-process agent uses, so that the server can't drift from what you tested. List them in a fixed order and mark them read-only. Let the role change what a tool returns, and shorten the tool list only when a role can't use a tool at all.

この部分はまだ翻訳されていないため、英語で表示している。

Carry the caller's role into every query

最終変更:版2026.11.15

A server that enforces chapter 9's access rules has to know whose rules to enforce, and that's the part an MCP server most often gets wrong. Revision 2026-07-28 has no protocol-level sessions: it removed the initialize handshake and the Mcp-Session-Id header, so every request stands alone (changelog). There's no session to hold a role. The specification gives two places for identity instead. A server that a host launches over stdio, for one person, "SHOULD NOT" use MCP's authorization and should take credentials from the environment (authorization). A server on HTTP derives the user from a verified access token: the specification's security guidance, on binding a server's state to a user, derives the user ID from the verified token, not from anything the client supplies (security best practices).

The tempting third place is a tool argument: give query_metric a role parameter and let the host fill it in. Then the role is whatever the caller sends, and the caller is a model that reads questions and, as chapter 9 showed, text inside the data. Three servers answer one request. Each receives gq-017, net revenue in each of "our countries" in 2025, asked by EMEA's regional lead, with "role": "analyst" added to the arguments. The first server takes the role as an argument. The second is the semantic server, built for EMEA's lead with build_server("regional_lead", "EMEA"). The third is built by server_from_environment(), which reads SHOP_ROLE and SHOP_REGION as a host would set them when it launches the server for one person. Last, the request runs once more on that third server's database, through the plain semantic layer with no policy, as the paragraph after the results explains.

role-bound-at-build.py Python 3.12.15 · anyio 4.16.0 · duckdb 2.0.0 · mcp 2.3.0 · pydantic 2.14.3 · pyyaml 6.0.3 · sqlglot 30.31.0 合格
"""gq-017 from EMEA's regional lead, sent with role "analyst": a server that takes the role as an argument obeys it,and one that binds the role when it is built ignores it, and queries a database that holds only the lead's rows.The `role as argument, countries` line shows every country a request-supplied role returns, and the `role bound atbuild, countries` line settles that a server built for the lead returns EMEA's countries only."""import anyiofrom mcp import Clientfrom mcp.server.mcpserver import MCPServerfrom lib.policies import PolicyLayer, PolicyToolbox, policy_forfrom lib.semantic import MetricRequest, loadfrom lib.semantic_server import build_server, server_from_environmentfrom lib.warehouse import connectcon, layer = connect(), load()naive = MCPServer("role-as-argument")@naive.tool()def query_metric(metrics: list[str], group_by: list[str] = [], filters: dict = {}, role: str = "analyst",                 region: str | None = None) -> list[list]:    """The anti-pattern: whoever calls the tool says who they are, and it queries the whole warehouse."""    toolbox = PolicyToolbox(con, PolicyLayer(layer, policy_for(role, region), con))    return [list(row) for row in toolbox.query_metric({"metrics": metrics, "group_by": group_by,                                                       "filters": filters}).answer.rows]request = {"metrics": ["net_revenue"], "group_by": ["order__country"], "filters": {"metric_time__year": 2025},           "role": "analyst"}                     # the lead's request, with a role the lead doesn't haveenvironment = {"SHOP_ROLE": "regional_lead", "SHOP_REGION": "EMEA"}   # what a host sets for a stdio serverasync def main():    servers = {"role as argument": naive, "role bound at build": build_server("regional_lead", "EMEA", con, layer),               "role from the environment": (stdio := server_from_environment(environment, con))}    for name, server in servers.items():        async with Client(server) as client:            result = (await client.call_tool("query_metric", request)).structured_content        rows = result["result"] if "result" in result else result["answer"]["rows"]        print(f"{name}, countries: {', '.join(row[0] for row in rows)}")        if "answer" in result:            provenance = result["answer"]["provenance"]            print(f"{name}, provenance: role {provenance['role']}, row filter {provenance['filters']['row filter']}")    # The policy bypassed: the plain semantic layer, which applies no role, on the stdio server's own database.    bypass = layer.query(stdio.database, MetricRequest.from_arguments({k: v for k, v in request.items() if k != "role"}))    print(f"role from the environment, no policy, countries: {', '.join(row[0] for row in bypass.rows)}")anyio.run(main)
出力python role-bound-at-build.py
role as argument, countries: AU, CA, DE, ES, FR, GB, JP, NL, SG, US
role bound at build, countries: DE, ES, FR, GB, NL
role bound at build, provenance: role regional_lead, row filter EMEA only
role from the environment, countries: DE, ES, FR, GB, NL
role from the environment, provenance: role regional_lead, row filter EMEA only
role from the environment, no policy, countries: DE, ES, FR, GB, NL

The server that takes the role as an argument returned AU, CA, DE, ES, FR, GB, JP, NL, SG, US: every country in the shop, because the request said "analyst" and the server believed it. The semantic server returned DE, ES, FR, GB, NL, EMEA's countries only, and its provenance says why: role regional_lead, row filter EMEA only. Its tools have no role parameter, so the extra argument went nowhere: the SDK validated the arguments against each tool's parameters, dropped the one it didn't know, and ran the call. The server built from the environment returned DE, ES, FR, GB, NL. Binding the role at build means one server per person, which is what stdio gives you: the host starts a process for its user, and the process lives as long as the host needs it (Choose stdio or Streamable HTTP).

The binding decides two things, and the database is the first. The book's primary access control is what the database allows each role: a read-only connection to that role's own views, which hold only its rows and columns, as chapter 7 built it, with chapter 9's policy rewrite as a second layer behind it. So build_server() doesn't take a connection to query. It takes the shop's warehouse, derives the role's policy, and opens the role's own database with agent_warehouse(shop, policy=policy, semantic=SEMANTIC_TABLES): chapter 7's database, plus the semantic layer's views and calendar as the role sees them, so that metrics can run on it. Every tool queries that database, and no caller can pair a role with another role's. The final step runs the lead's request through the plain semantic layer, which applies no role, on the environment server's own database. It returned DE, ES, FR, GB, NL: with the policy bypassed, there are still only EMEA's rows to read.

The second is what counts as forbidden, which the policy alone decides: a filter on region with any value but the lead's own is forbidden. Any other value the lead's rows don't hold, such as another region's country, gets a correctable error listing the lead's own values, whether it exists elsewhere or not, so it reveals nothing (chapter 9).

A server on HTTP serves many people, so it can't bind a role when it starts. It needs the role on each request, from the token. In the Python SDK, the server is given a TokenVerifier whose verify_token() returns an AccessToken with the client's ID, its scopes and the token's claims, and a tool reads the verified token with get_access_token() (mcp/server/auth/provider.py, mcp/server/auth/middleware/auth_context.py). The server would map a claim to a role and region there, and choose that role's database and policy for the call. The token must have been issued for this server: servers must check that each access token was issued for them, as its intended audience (authorization), which Model Context Protocol in Practice builds in bind each token to one server. Scopes don't replace the access rules. A scope can say that a token may call query_metric; only the database and the policy can say which rows it reads, and the specification's security guidance lists trusting the scopes a token claims, with no server-side check, as a common mistake (security best practices). Nothing here runs this path, because an in-memory client has no HTTP layer, so no bearer token reaches the server, and get_access_token() returns None there.

Working rule: Bind the role where the person was authenticated, never in a tool's arguments. For a stdio server, the host passes the role in the environment, and the server opens that role's read-only database and builds its policy once. For an HTTP server, take the role from a verified token issued for this server, on every request, and enforce the role's rows in the database and the policy whatever the token's scopes say. Leave role out of every input schema, so there's nothing for a model or a question to fill in, and log any argument a tool ignores, role first, because one is a sign that text the model read is steering it (treat ticket text as untrusted data).

この部分はまだ翻訳されていないため、英語で表示している。

Return answers with their provenance

最終変更:版2026.11.15

With the role bound, the server's answers are right for the person asking. The host still has to know what each answer is: which metric produced it, with which filters, for which role and from data how fresh. Chapter 1 called that an answer's provenance, and the in-process agent keeps it in Answer.provenance. Over MCP, a tool can declare an outputSchema and return structuredContent that conforms to it, and a tool that does "SHOULD also return the serialized JSON in a TextContent block" (tools). Structured content is what lets a host's code, rather than its model, read an answer's role and filters. Model Context Protocol in Practice shows how the SDK builds the schema from a return type in return structured content with an output schema.

Every tool of the semantic server returns a ToolReply, a pydantic model with two fields: text, the text the in-process tool shows the model, and answer, the answer with its rows and provenance, or nothing when the result doesn't end the run. Failures take two routes. The MCP specification reports a tool execution error as a result with isError set, with "actionable feedback that language models can use to self-correct" (tools). A request with a misspelt dimension is that kind of failure, so the server raises the SDK's ToolError with chapter 6's validation message. A request the role may not make isn't, and the server returns it as an answer that declines, with a reason that starts "forbidden", as PolicyToolbox does in process. Each route is worth seeing from the host's side: the finance team's refund rate by region for fiscal 2026, the same with order_region for order__region, and the support team's net revenue for 2025.

tool-result-with-provenance.py Python 3.12.15 · anyio 4.16.0 · duckdb 2.0.0 · mcp 2.3.0 · pydantic 2.14.3 · pyyaml 6.0.3 · sqlglot 30.31.0 合格
"""What a host receives from query_metric: an answer with its provenance as structured content, a request the modelcan correct as a tool error, and a request the role may not make as an answer that declines. The `text block is the same JSON: yes` line settles thatthe finance answer's text matches its structured content, and `support, net revenue` with `is_error: False` and`answered: no` settles that a forbidden request declines rather than errors."""import jsonimport anyiofrom mcp import Clientfrom lib.semantic import loadfrom lib.semantic_server import build_serverfrom lib.warehouse import connectcon, layer = connect(), load()asks = {"finance, refund rate": ("finance", {"metrics": ["refund_rate"], "group_by": ["order__region"],                                             "filters": {"metric_time__fiscal_year": 2026}}),        "finance, misspelt dimension": ("finance", {"metrics": ["refund_rate"], "group_by": ["order_region"]}),        "support, net revenue": ("support", {"metrics": ["net_revenue"], "filters": {"metric_time__year": 2025}})}async def main():    for name, (role, request) in asks.items():        async with Client(build_server(role, shop=con, layer=layer)) as client:            tool = next(t for t in (await client.list_tools()).tools if t.name == "query_metric")            result = await client.call_tool("query_metric", request)        print(f"{name}, is_error: {result.is_error}")        if result.is_error:            print(f"{name}, text: {result.content[0].text}")            continue        answer = result.structured_content["answer"]        answered = answer["answered"]        assert answered == (role != "support")   # support may see no revenue, so its answer declines        print(f"{name}, answered: {'yes' if answered else 'no'}")        same = json.loads(result.content[0].text) == result.structured_content   # the specification asks for this JSON in the text block        assert same        print(f"{name}, text block is the same JSON: {'yes' if same else 'no'}")        if answer["answered"]:            print(f"{name}, rows: {', '.join(f'{region} {rate:.2%}' for region, rate in answer['rows'])}")            print(f"{name}, provenance fields: {', '.join(answer['provenance'])}")            print(f"{name}, provenance: {json.dumps({k: v for k, v in answer['provenance'].items() if k != 'sql'})}")        else:            print(f"{name}, reason: {answer['reason']}")    print(f"output schema requires: {', '.join(tool.output_schema['required'])}")anyio.run(main)
出力python tool-result-with-provenance.py
finance, refund rate, is_error: False
finance, refund rate, answered: yes
finance, refund rate, text block is the same JSON: yes
finance, refund rate, rows: AMER 7.11%, APAC 6.02%, EMEA 8.45%
finance, refund rate, provenance fields: source, metric, sql, filters, role, data_as_of
finance, refund rate, provenance: {"source": "metric", "metric": "refund_rate", "filters": {"metric_time__fiscal_year": 2026}, "role": "finance", "data_as_of": "2026-06-27 02:00:00"}
finance, misspelt dimension, is_error: True
finance, misspelt dimension, text: Error executing tool query_metric: error: request rejected: refund_rate can't use dimension 'order_region'; did you mean order__region?
support, net revenue, is_error: False
support, net revenue, answered: no
support, net revenue, text block is the same JSON: yes
support, net revenue, reason: forbidden: the support role may not see net_revenue
output schema requires: text, answer

A host's code can check each answer field by field. Finance's refund rates came back as structured rows, AMER 7.11%, APAC 6.02%, EMEA 8.45%, computed on finance's own database, whose copy of the calendar gives each day its fiscal year. The provenance has these fields: source, metric, sql, filters, role, data_as_of. Without the SQL, the provenance reads {"source": "metric", "metric": "refund_rate", "filters": {"metric_time__fiscal_year": 2026}, "role": "finance", "data_as_of": "2026-06-27 02:00:00"}. The text block carries the same JSON as the structured content, and the output schema requires text, answer.

The misspelt dimension came back with is_error set and the text "Error executing tool query_metric: error: request rejected: refund_rate can't use dimension 'order_region'; did you mean order__region?". The suggestion is chapter 6's, and the model can act on it. The words before it aren't the server's: the SDK's tool wrapper puts "Error executing tool" and the tool's name in front of the message of any ToolError a tool raises (mcp/server/mcpserver/tools/base.py). The in-process agent never showed the model that prefix, and Answer questions through a host measures what it changes.

Support's net revenue came back without is_error, as an answer that declines, with the reason "forbidden: the support role may not see net_revenue". We return a refusal as an answer, not an error, on purpose. An error invites the model to correct its request and try again, and there's no request support can correct into net revenue. A decline ends the run, as it did in chapter 9, and the host's code can see from the structured reason that the access rules, not the model, made the decision.

Working rule: Return a pydantic model from every tool, so that each answer travels as structured content with its rows, its role, its filters and its data's freshness, and a host's code can check them. Raise a tool error for a request the model can fix, with a message that says how. Return a refusal for access as an answer that declines, with its reason, so the host ends the run instead of letting the model try another way in.

サーバーをメモリ内でテストする

最終変更:版2026.11.12

セマンティックサーバーの構造化された回答は、フィールド単位でテストできる。重要なテストはアクセスに関するものであり、あるロール向けに構築したサーバーが、別のロールとして回答することは決してあってはならない。このようなテストは変更のたびに実行すべきであり、そのためポートやプロセスを必要としてはならない。Python SDK の Client は、URL の代わりにサーバーオブジェクトを渡すと、同じプロセス内のそのサーバーに接続する。また raise_exceptions=True を指定すると、ツール本体の外で起きた失敗が実際のメッセージとともに返る。これについては Model Context Protocol in Practice のツールをメモリ内でテストするで説明されている。同じ節には、ヘッダーやオリジンチェックなど、そのようなテストでは扱えないものも挙げられている。

サーバーのテストはそれぞれ、1 つのロール向けにサーバーを構築し、メモリ内クライアントを通じて 1 つのツールを呼び出し、構造化コンテンツに対してアサートする。テストが対象とするのは、第 9 章で測定したルールと、その下にあるデータベースである。具体的には次のとおりである。EMEA のリードは gq-017 の正解結果(ゴールデン結果)を得る。EMEA のリードが APAC を要求した場合は、禁止として拒否される。リードのサーバー自身のデータベースを、ポリシーを介さずに直接クエリしても、他のリージョンの注文は含まれていない。サポートのカタログは、売上を読み取るすべての指標を隠し、それらだけを隠す。マーケティングの小さなグループは抑制される。綴りを誤ったディメンションはツールエラーとなり、正しいものが提示される。本書は特定のテストランナーを指定しないため、このファイルは lib/semantic_server.py にある小さなヘルパーを使う。pytest の下では、それぞれが通常の非同期テストになる。

semantic-server-tests.py Python 3.12.15 · anyio 4.16.0 · duckdb 2.0.0 · mcp 2.3.0 · pydantic 2.14.3 · pyyaml 6.0.3 · sqlglot 30.31.0 合格
"""In-memory tests of the semantic server, one role per server, and one check that a test can fail. The prose'spoint rests on the final line: the lead's request on an analyst's server must differ from the lead's gold."""import anyiofrom lib.golden import golden_result, load_golden, results_matchfrom lib.semantic import loadfrom lib.semantic_server import build_server, call, run_testsfrom lib.warehouse import connectcon, layer = connect(), load()server = lambda role, region=None: build_server(role, region, con, layer)      # each on the role's own databasegold = golden_result(con, next(q for q in load_golden() if q.question_id == "gq-017"))lead_request = {"metrics": ["net_revenue"], "group_by": ["order__country"], "filters": {"metric_time__year": 2025}}HIDDEN_FROM_SUPPORT = {"average_order_value", "gross_revenue", "line_net_revenue", "net_revenue", "refund_rate"}async def test_lead_answer_matches_the_golden_result():    result = await call(server("regional_lead", "EMEA"), "query_metric", lead_request)    assert results_match(result.structured_content["answer"]["rows"], gold)async def test_lead_cannot_ask_for_another_region():    result = await call(server("regional_lead", "EMEA"), "query_metric", {"metrics": ["orders"],                        "filters": {"order__region": "APAC"}})    assert not result.is_error and result.structured_content["answer"]["reason"].startswith("forbidden")async def test_lead_database_holds_no_other_region():        # the policy layer bypassed: SQL straight to the database    regions = server("regional_lead", "EMEA").database.execute("SELECT DISTINCT region FROM analytics.fct_orders")    assert regions.fetchall() == [("EMEA",)]async def test_support_catalog_hides_every_revenue_metric():    listed = (await call(server("support"), "list_metrics", {})).structured_content["text"]    assert HIDDEN_FROM_SUPPORT == set(layer.metrics) - {line[2:].split(":")[0] for line in listed.splitlines()}async def test_marketing_small_groups_are_suppressed():    result = await call(server("marketing"), "query_metric", {"metrics": ["orders"], "group_by":                        ["order__channel", "order__country"], "filters": {"metric_time__month": "2026-06"}})    assert any("(under 10)" in row for row in result.structured_content["answer"]["rows"])async def test_unknown_dimension_is_a_tool_error_with_a_hint():    result = await call(server("finance"), "query_metric", {"metrics": ["orders"], "group_by": ["order_region"]})    assert result.is_error and "did you mean order__region?" in result.content[0].textasync def main():    passed = await run_tests(globals())    print(f"tests passed: {passed} of {passed}")    unbound = (await call(server("analyst"), "query_metric", lead_request)).structured_content["answer"]["rows"]    differs = not results_match(unbound, gold)   # the analyst's server returns every country, so the lead's gold must not match    assert differs    print(f"the lead's request on an analyst's server differs from the lead's gold: {'yes' if differs else 'no'}")anyio.run(main)
出力python semantic-server-tests.py
test_lead_answer_matches_the_golden_result: passed
test_lead_cannot_ask_for_another_region: passed
test_lead_database_holds_no_other_region: passed
test_support_catalog_hides_every_revenue_metric: passed
test_marketing_small_groups_are_suppressed: passed
test_unknown_dimension_is_a_tool_error_with_a_hint: passed
tests passed: 6 of 6
the lead's request on an analyst's server differs from the lead's gold: yes

この実行は 6 of 6 を報告する。テストが通ることに意味があるのは、失敗しうる場合だけである。そのためこの実行は、最初のテストのリクエストをアナリストのサーバーにも送り、その結果をリードのゴールデン結果と比較する。結果はリードのゴールデン結果と異なるが、アナリストのサーバーはすべての国を返すので、これは期待どおりである。したがって、最初のテストは、バインディングを失ったサーバーを検出できる。

これらのテストが検査するのはサーバーであり、トランスポートではない。テストは SDK の引数検証、構造化出力、エラー処理を通る。これはエラープレフィックスの出どころでもある。しかし、どのリクエストもトークンを運ばない。HTTP でデプロイする場合は、少なくとも 2 つのテストを HTTP 越しに追加する。1 つは 2 つのロールのトークンを送り、それぞれが自分の行を得ることを確認するもの、もう 1 つは別のサーバー向けに発行されたトークンを送り、拒否されることを確認するものである。

実践ルール: 各ロールのルールは、ロールごとに 1 つのサーバーを用意し、構造化された回答に対してアサートするメモリ内クライアントでテストする。その際、バインディングが誤っているときに失敗するチェックを含める。期待値にはゴールデンクエスチョンの結果を使い、テストとスコアが何を正しいとするかについて一致するようにする。メモリ内クライアントが送れないものについては、トークンを最優先として、HTTP 越しのテストを追加する。

この部分はまだ翻訳されていないため、英語で表示している。

Answer questions through a host

最終変更:版2026.11.15

The tests show that the semantic server answers each tool call as the in-process agent would. The last question is whether an agent answers as well through it. A host is the application that runs the model and calls the server's tools for it, and the host here is the book's own: chapter 1's agent loop, run_agent() in lib/agent.py, with chapter 6's prompt and the recorded model, Qwen3-4B-Instruct-2507, that every chapter replays.

The only new piece is ServerToolbox in lib/semantic_server.py. ServerToolbox has the call() method the loop expects, and makes each call through an MCP client. ask_through_server() opens a client on a server and runs the loop in a worker thread, so that each tool call can reach the server on the event loop. For gq-017, the host made the calls list_metrics, query_metric: the first fills the prompt's catalog, and the second carries the model's request. A model's call that isn't a JSON object, or names a tool the server doesn't list, gets the in-process agent's message from the host without reaching the server, with the tools named in the in-process order. Model Context Protocol in Practice builds a general host in run the host loop; this one stays as thin as the book's loop.

Replay needs the model to see exactly what it saw when it was recorded, and over MCP it mostly does: the catalog and the prompt are the same, and so is every successful tool result's text. A tool error is the exception. Its text carries the SDK's prefix, so the model's next call has a prompt that no earlier recording holds. The recording mcp-host-runs, made with recordings/record_mcp_host.py, holds the replies to those calls only, from the same pinned model and settings. Every golden question runs twice, in process as chapter 9 measured it and through a server built for the question's role, and the example compares the two outcomes question by question.

host-asks-the-server.py Python 3.12.15 · anyio 4.16.0 · duckdb 2.0.0 · mcp 2.3.0 · pydantic 2.14.3 · pyyaml 6.0.3 · sqlglot 30.31.0 合格
"""The book's agent as an MCP host on every golden question, each tool on the asker's server, against chapter 9.The `same outcome as in process` line settles how many outcomes held, and the two questions that changed,`gq-013` and `gq-014`, each met a tool error."""from collections import Counterimport anyiofrom lib.agent import run_agentfrom lib.golden import golden_result, grade, load_goldenfrom lib.metric_tools import catalogfrom lib.model import RecordedModelsfrom lib.policies import PolicyLayer, PolicyToolbox, policy_forfrom lib.prompts import metrics_first_promptfrom lib.semantic import loadfrom lib.semantic_server import ask_through_server, build_serverfrom lib.warehouse import connectcon, layer = connect(), load()model = RecordedModels("metric-agent-runs", "policy-agent-runs", "mcp-host-runs")   # ch 11 recorded the restasync def main():    counts, changed, details, errors = Counter(), [], [], 0    for q in load_golden():        seen_as = PolicyLayer(layer, policy_for(q.role, q.region or None), con)        local = run_agent(q.question, metrics_first_prompt(catalog(seen_as)), model, PolicyToolbox(con, seen_as), 4)        trace, calls = await ask_through_server(build_server(q.role, q.region or None, con, layer), q.question, model)        outcomes = [grade(q, t.answer, golden_result(con, q)) for t in (local, trace)]        counts[q.split, q.kind, "questions"] += 1        counts[q.split, q.kind, "correct"] += outcomes[1] == "correct"        errors += any("is_error" in c for c in calls)        if outcomes[0] != outcomes[1]:            changed.append(f"{q.question_id} ({q.split}, {q.kind}): {outcomes[0]} in process, "                           f"{outcomes[1]} over MCP, by {trace.steps[-2].tool}")   # the last tool call ended the run            details += [f"{q.question_id} first request's filters: {trace.steps[0].arguments['filters']}",   # the model's first call                        f"{q.question_id} asked: {trace.answer.reason.splitlines()[0]}"]        if q.question_id == "gq-017":            print(f"gq-017 calls: {', '.join(calls)}")    for split in ("dev", "test"):        for kind in ("answer", "decline", "forbidden"):            print(f"{split} {kind} correct over MCP: {counts[split, kind, 'correct']} of "                  f"{counts[split, kind, 'questions']}")    print(f"runs with a tool error: {errors}")    total = len(load_golden())    print(f"same outcome as in process: {total - len(changed)} of {total}")    print("\n".join(changed + details) or "no outcome changed")   # one line per changed question, then detailsanyio.run(main)
出力python host-asks-the-server.py
gq-017 calls: list_metrics, query_metric
dev answer correct over MCP: 11 of 17
dev decline correct over MCP: 3 of 4
dev forbidden correct over MCP: 3 of 3
test answer correct over MCP: 6 of 17
test decline correct over MCP: 4 of 4
test forbidden correct over MCP: 3 of 3
runs with a tool error: 11
same outcome as in process: 46 of 48
gq-013 (dev, answer): correct in process, declined over MCP, by ask_back
gq-014 (dev, answer): correct in process, declined over MCP, by ask_back
gq-013 first request's filters: {'order__order_date': '2026-05'}
gq-013 asked: Are you looking for orders in the entire month of May 2026, or specifically on a single day in May 2026?
gq-014 first request's filters: {'order__order_date': '2026-05'}
gq-014 asked: Do you mean orders placed in the entire month of May 2026 or on a specific day in May 2026?

Through the server, the agent kept its in-process outcome on 46 of 48 questions. On the dev split's answer questions, the golden questions used while building, it scored 11 of 17, against 13 of 17 in process.

On the test split the score matched the in-process one: 6 of 17, against 6 of 17.

Every forbidden question was declined, 3 of 3 on dev and 3 of 3 on test, because the policy hides what the role may not see and refuses what it may not ask, as in chapter 9.

Only gq-013 and gq-014 changed, and both went through a tool error. 11 runs met one, and the rest kept their outcome. Both ask about orders in May 2026, and the model's first request had the filters {'order__order_date': '2026-05'}, which validation rejects with a hint to filter metric_time__month instead. In process, the model followed the hint and got the right count. Over MCP, it read the same hint after "Error executing tool query_metric:", and asked the person back instead: "Are you looking for orders in the entire month of May 2026, or specifically on a single day in May 2026?"

The printed line for gq-013 reads correct in process, declined over MCP, by ask_back, and gq-014's is the same. That's one sample per run at temperature 0.7, so it doesn't show that the prefix caused the change, only that a different text gave a different draw. It does show that an outcome can move with nothing changed but the transport's wording, and that only a score on the golden questions finds it.

Treat what the server returns as data in the host as well. OWASP's Top 10 for LLM applications lists an MCP server's output among the carriers of indirect prompt injection (OWASP, LLM01:2026), and a metric answer carries values from the warehouse, such as product names, that chapter 9 showed can hold instructions. The host shows the person the structured answer with its provenance, and never a model's retelling of it unchecked. Model Context Protocol in Practice covers the host's side in treat ticket text as untrusted data.

Working rule: Put the server under the host you already measured, and score it on the golden questions before anyone uses it, because the transport can change what the model reads. Compare outcomes question by question with the in-process runs, and read every run that changed. Record what the new text produces rather than editing the server's messages to match old recordings, and show people the structured answer with its provenance.

本番環境で何が問題になるか

最終変更:版2026.11.12

MCP 経由で提供されるセマンティックレイヤーのリスクは、その境界部分にある。誰が接続しているか、ホストがほかに何を接続しているか、そしてどの SDK がサーバーを支えているか、である。

1 つのプロセスが複数の人にサービスを提供する。 1 つのロールに束縛された stdio サーバーが安全なのは、1 人のホストがそれを所有している間だけである。これを共有プロセスで包んだり、トークンなしで HTTP の背後に置いたりすると、全員が、そのサーバーを起動した人のロールを得ることになる。ここで構築したセマンティックサーバーは監査ログを書き出さないため、デプロイでは、サーバーが構築された対象のプリンシパルとともに、各回答について第 9 章のエントリーを記録すべきである。そこで気づけるのは、複数のユーザーやホストからリクエストが来ているプリンシパルや、1 人では出せない頻度でリクエストが来ているプリンシパルである。複数の人にサービスを提供するのは HTTP の場合に限り、ロールは各リクエストのトークンから取る。

トークンのロールとポリシーファイルが食い違う。 roles.toml にないロールを名指しするクレームや、リージョンを持たないリージョナルリードは、フェイルクローズで失敗させなければならない。policy_for() はその両方で PolicyError を送出するが、これを捕捉して既定のロールにフォールバックするサーバーは、束縛を無効にしてしまっている。クレームからロールへの対応は、すべてのロールのトークンと、ロールを持たないトークンでテストする。

サーバーの接続はそのロールより優先される。 ポリシーはクエリを絞り込むが、クエリが何に到達できるかを決めるのはデータベースである。リードのロールを束縛しておきながらアナリストの接続でクエリを実行するサーバーは、バグ 1 つで漏えいに至る。build_server() が行うように、ロールを束縛するときにそのロール専用の読み取り専用データベースを開き、テストが行うように、その接続が別のリージョンの行を読めないことをテストで確認する。

ホストが古いカタログをキャッシュする。 リビジョン 2026-07-28 では、リスト結果に有効期間とキャッシュスコープを持たせられるため、ホストはそれらを再利用してよい(Cache list results)。list_metrics はツール呼び出しなので、プロトコルはそのカタログをキャッシュしないが、それでもキャッシュするホストは、ポリシーが除外した後のメトリクスを表示してしまう。アクセスルールは依然としてリクエストを拒否するので、代償は、モデルが自ら辞退したはずの場面で forbidden による拒否が返ることである。

SDK のアップグレードでモデルが読む内容が変わる。 ツールエラーの接頭辞も、引数検証エラーの文面も、サーバーのコードではなく SDK に由来する。新しいリリースでどちらかの文言が変わることがあり、エラー後のエージェントの挙動もそれに伴って変わる。SDK を固定し、アップグレードのたびにホスト経由でゴールデン質問を再実行し、結果が変わった実行を読む。

2 つのサーバーが同じメトリクスを記述する。 ベンダーも MCP でセマンティックレイヤーを提供している。dbt の MCP サーバーは、dbt プラットフォーム上のプロジェクト向けに、list_metrics、get_dimensions、query_metrics などの名前の Semantic Layer ツールを提供する(dbt Labs)。また Snowflake のマネージド MCP サーバーは、Cortex Analyst を通じてセマンティックビューに対する質問に答え、接続ユーザーの既定のロールと、ツールごとの個別の権限付与を用いる(Snowflake)。これらはベンダーが自社製品について述べた説明である。ホストがベンダーのサーバーとあなたのサーバーの両方を接続すると、そのモデルは、2 通りの定義を持つ 2 つの list_metrics ツールを目にする。各ホストにはセマンティックレイヤーごとに 1 つのサーバーを与え、どうしても 2 つ必要な場合は、Model Context Protocol in Practice がサーバー間でツールに名前を付けるで示すように、ツール名で区別する。

古いリビジョンのクライアントが接続する。 mcp 2.3.0 は、2025 年のリビジョンのクライアントにも旧来のハンドシェイクで対応しており、dbt のサーバーは SDK の 1.x 系列に固定されている(dbt-mcp)。セマンティックサーバーのツールはリビジョンに依存しないが、HTTP デプロイのセッションとキャンセルは依存する。これについては Model Context Protocol in Practice の移行期間中に新旧のクライアントへ対応するで扱っている。

実践ルール: stdio サーバーは 1 人につき 1 つ動かすか、HTTP で各リクエストのトークンからロールを取る。ポリシーファイルが知らないクレームはすべてフェイルクローズにする。共有のデータベースではなく、ロール専用の読み取り専用データベースでクエリを実行する。SDK を固定し、変更のたびにホスト経由でゴールデン質問を再実行する。各ホストにはセマンティックレイヤーごとに 1 つのサーバーを置き、すべての回答に監査エントリーを記録し、複数の人が共有しているように見えるプリンシパルがないかそれを読む。

この章で下した決定

本書はここで終わる。出発点は、スキーマに対して SQL を書き、正解のある質問の大半を誤るエージェントであった。いまでは、店が使える版を構築できる。その版は、まず管理された指標に問い合わせ、SQL はそのロールの読み取り専用データベース上でガードの内側に限って書き、答えられないときは断り、各ロールが閲覧できる範囲に収め、これらすべてを MCP によって任意のホストへ提供する。何より、自分の作業から書いた正解付きの質問で個々の変更を測定できるので、次に行う変更は証明できるものになる。

  • セマンティックサーバーは第 6 章の五つのツールを提供する。 各ツールは第 9 章の PolicyToolbox への薄い呼び出しであり、サーバーとインプロセスのエージェントは同じコードを実行する。
  • ツール一覧は全ロールで共通である。 名前順に並べ、読み取り専用と明示する。ロールによって変わるのは、list_metrics やその他のツールが返す内容である。
  • ロールはサーバーを構築するときに結び付ける。 stdio では環境から、HTTP ではリクエストごとに検証済みのトークンから決める。どのツールも role 引数を取らない。
  • 各サーバーは、そのロール専用の読み取り専用データベースに問い合わせる。 これは第 7 章のデータベースに、セマンティックレイヤーのビューとカレンダーを加えたものである。ポリシーは第二の層である。
  • すべてのツールは構造化コンテンツを返す。 モデルに示すテキストと、行と出所を含む回答の二つである。
  • モデルが修正できるリクエストはツールエラーとし、ロールに許されないリクエストは断りの回答とする。 断りの理由は "forbidden" で始める。
  • サーバーはメモリ内で、サーバー 1 台につき 1 ロールでテストする。 正解の結果と照合し、結び付けが誤っていれば失敗する検査を含める。
  • HTTP の経路は説明するだけで、実行はしない。 例はソケットを開かず、メモリ内のクライアントはトークンを持たない。そのため、検証済みトークンからロールへの対応付けには、HTTP 越しの専用のテストが必要である。
  • ホストは本書自身のループとプロンプトである。 以前の記録が保持する呼び出しは再生する。mcp-host-runs が保持するのは、SDK が変更したエラーテキストの後に続く呼び出しだけである。

この版における本章

第2026.11.15版2026年11月19日時点で例が通過この章の5 例件のうち5件が合格

英語版の書籍(版2026.11.15)から翻訳した。

この節を引用する

形式

いずれの形式も、本訳書が従う英語版の書籍を出典として示す。

いずれの形式もこの版を明示している。そのリンクは現行版を開き、節の見出しには本文が最後に変更された日付が示される。アクセス日と取得日は、これを開いた日である。

このページの内容

全11章中の第11章: Serve the semantic layer over MCP

  1. Turn metrics into tools
  2. Carry the caller's role into every query
  3. Return answers with their provenance
  4. サーバーをメモリ内でテストする
  5. Answer questions through a host
  6. 本番環境で何が問題になるか
  7. この章で下した決定

ページの先頭に戻るすべての章