MCP security glossary
Twenty-eight terms are defined here in plain language, from tool description, tool schema and server manifest to DNS rebinding, localhost binding and server pinning. Each entry gives a two to four sentence definition, one sourced example and links to related terms, with sources read on 16 Nov 2026.
Facts read on .
28 terms
- Command injection: Command injection is a flaw in which text from an untrusted source ends up interpreted by a shell or operating system call.
- DNS rebinding: DNS rebinding is a technique in which a domain name first resolves to a public address and later to a local one, letting a remote web page reach a service bound to the user's machine.
- Dynamic Client Registration: Dynamic Client Registration (RFC 7591) is the OAuth mechanism by which a client registers with an authorization server at run time.
- Localhost binding: Localhost binding is the practice of having a server listen only on the loopback address, 127.0.0.1, instead of all network interfaces.
- MCP authorization: MCP authorization is the OAuth 2.1-based profile that lets a client obtain tokens for a protected remote MCP server.
- MCP config file: An MCP config file is the settings file in which a client records its MCP servers: the command or URL for each, its arguments and its environment variables.
- MCP elicitation: MCP elicitation is a client feature that lets a server request more information from the user during an interaction.
- MCP Inspector: The MCP Inspector is the reference developer tool for testing and debugging MCP servers, shipped as the package @modelcontextprotocol/inspector.
- MCP Registry: The MCP Registry is the official centralized metadata repository for publicly accessible MCP servers.
- MCP resource: An MCP resource is a piece of data that a server shares with a client, identified by a URI, such as a file, a database schema or application-specific information.
- MCP roots: MCP roots are a client feature that tells a server which directories and files the client considers relevant.
- MCP sampling: MCP sampling is a client feature that lets a server request a completion from the user's language model through the client.
- MCP session: An MCP session was a connection-scoped state set up by an initialize handshake in revisions up to 2025-11-25.
- MCP transport: An MCP transport is the binding that defines how JSON-RPC messages are framed and delivered between a client and a server.
- npx launcher: The npx launcher is the npm tool that downloads and runs a package in one command, and it is a common way to start a local MCP server.
- Package supply chain: The package supply chain, for MCP, is the set of packages, dependencies and registries that deliver a server to a machine.
- Path traversal: Path traversal is a flaw in which a path supplied to a tool reaches files outside the directory the tool was meant to stay in.
- Protected resource metadata: Protected resource metadata is a document defined in RFC 9728 that a protected server publishes to describe itself, including which authorization servers it trusts.
- Resource indicators: Resource indicators are an OAuth extension (RFC 8707) in which the client states which resource server a requested token is meant for.
- Server manifest: A server manifest is a metadata file that names an MCP server, says where its code or endpoint lives and how to launch it.
- Server pinning: Server pinning is the practice of locking an MCP server to a reviewed version and detecting any change afterward.
- Server provenance: Server provenance is the record of who published an MCP server, from which source, and whether the package you install matches that source.
- SSRF: Server-side request forgery is an attack in which a program is induced to make HTTP requests to destinations it should not reach, such as internal services or cloud metadata endpoints.
- Tool annotations: Tool annotations are optional properties on a tool definition that describe its behavior, for example whether it only reads data or can destroy it.
- Tool description: A tool description is the text a server attaches to each tool so the model can decide when and how to call it.
- Tool schema: A tool schema is the JSON Schema in a tool definition, called inputSchema, that declares the arguments a tool accepts and their types.
- Tool shadowing: Tool shadowing is an attack in which a malicious server's tool description manipulates how the agent behaves with tools that belong to other, trusted servers.
- Typosquatted server: A typosquatted server is an MCP server package whose name closely imitates a trusted one so that a typing error or a quick glance installs it instead.