← Mathematical compendium

Published equation contexts

harm(scope)  =  p(misuse)⋅blast_radius(scope)\text{harm}(\text{scope}) \;=\; p(\text{misuse}) \cdot \text{blast\_radius}(\text{scope})

Why this formula appears here

That architecture is a specific case of a more general primitive already standardized outside MCP. RFC 9396 defines authorizationdn_details , an OAuth 2.0 extension letting a client request structured, fine-grained permissions — its own example is the difference between “read access to a profile” and “transfer 45 euros to a named merchant” — instead of the flat, coarse strings that scope provides on its own [ 7 ] . MCP’s step-up scoping is a narrower instance of the same idea: authorization as a set of bounded, named permissions rather than a single yes/no grant. The dual-control key-ceremony rig — two independent credentials, neither sufficient alone, both required before a shared grant…

Read the full article-specific guide →

Read the representative guide

How to interpret it

Read it with the definitions, units, and assumptions supplied by the article.

Research cited beside this formula

Published contexts (1)

A symbol can carry a different meaning in another article. Each occurrence keeps its own guide and term definitions.

harm(scope)  =  p(misuse)⋅blast_radius(scope)\text{harm}(\text{scope}) \;=\; p(\text{misuse}) \cdot \text{blast\_radius}(\text{scope})

Equation 1 · AI Infrastructure

Tool Protocols and the Model Context Protocol in 2035 — Scenarios, Signals, and Falsifiable Predictions

This equation states an equality: the expressions on both sides have the same value under the article’s assumptions.

That architecture is a specific case of a more general primitive already standardized outside MCP. RFC 9396 defines authorizationdn_details , an OAuth 2.0 extension letting a client request structured, fine-grained permissions — its own example is the difference between “read access to a profile” and “transfer 45 euros to a named merchant” — instead of the flat, coarse strings that scope provides on its own [ 7 ] . MCP’s step-up scoping is a narrower instance of the same idea: authorization as a set of bounded, named permissions rather than a single yes/no grant. The dual-control key-ceremony rig — two independent credentials, neither sufficient alone, both required before a shared grant…

Equation guide → · Article →