Equation 16 · How Tool Protocols and the Model Context Protocol Actually Work
What does this equation mean?
Read the formula alongside the article passage below. Each part has a deeper page with its role in the equation, the supporting passage and nearby citations.
This mathematical expression combines the displayed quantities; its precise role follows from the surrounding article text. Read the equation part by part below; each part has a contextual explanation and a link to its mathematical background.
Read it piece by piece
Symbol T_t
is a part of this expression. Its role is fixed by the surrounding article and by the operations shown in the formula.
subscript
The lower label selects a particular version, component, or indexed member of the quantity. For example, x₀ and xₜ can be values at different positions.
How to interpret it
Read this expression with the definitions, units, and assumptions supplied by the article.
What the article says around this equation
None of the mechanisms above stop a server from writing a dishonest description . Invariant Labs’ April 2025 disclosure of what it named tool poisoning attacks demonstrated exactly that gap: a tool description can carry hidden instructions inside it — in their proof of concept, wrapped in an <IMPORTANT> tag — that a model reads in full as part of while a host’s simplified UI shows the user only a short summary. Their working example was an innocuous-looking addition tool whose hidden instructions told the model to read local SSH keys and configuration files and smuggle their contents out through an unrelated parameter, while producing a normal-looking response to the user [ 7 ]…
Read the full surrounding passage
None of the mechanisms above stop a server from writing a dishonest description . Invariant Labs’ April 2025 disclosure of what it named tool poisoning attacks demonstrated exactly that gap: a tool description can carry hidden instructions inside it — in their proof of concept, wrapped in an <IMPORTANT> tag — that a model reads in full as part of while a host’s simplified UI shows the user only a short summary. Their working example was an innocuous-looking addition tool whose hidden instructions told the model to read local SSH keys and configuration files and smuggle their contents out through an unrelated parameter, while producing a normal-looking response to the user [ 7 ] . Nothing about that violates the wire format. The description field is a string; the protocol delivers it faithfully; the attack lives entirely in the fact that the model reads the whole string and a human typically does not.
Sources cited in the surrounding passage
These citations give research context. Read each source to check which claims it supports.
Return to How Tool Protocols and the Model Context Protocol Actually Work