# Human confirmation, defined with a sourced example

GLOSSARY, read 10 Nov 2026

**The short answer.** A step where a person approves a tool call before it runs. The MCP specification keeps a human in the loop with the ability to deny invocations. Some servers ask through the protocol. Per AWS Labs' README, in read-write mode the Redshift server asks for confirmation on each write through MCP elicitation, unless UNSAFE_SKIP_WRITE_CONFIRMATION is set.

## Definition

A step where a person approves a tool call before it runs. The MCP specification keeps a human in the loop with the ability to deny invocations. Some servers ask through the protocol.

## Example from a real server

**Example.** Per AWS Labs' README, in read-write mode the Redshift server asks for confirmation on each write through MCP elicitation, unless UNSAFE_SKIP_WRITE_CONFIRMATION is set.

## Related terms

- [impact analysis](/glossary/impact-analysis/): The question of what breaks downstream if an asset changes or fails.
- [input schema](/glossary/input-schema/): A JSON Schema that states which arguments a tool accepts, their types and which are required or limited to set values.
- [Genie space](/glossary/genie-space/): A Databricks workspace for asking questions of chosen tables in natural language, set up with curated instructions.

## Where to read more

- [The directory](/)
- [All glossary terms](/glossary/)

## Sources

- raw.githubusercontent.com/awslabs/mcp/main/src/redshift-mcp-server/README.md: https://raw.githubusercontent.com/awslabs/mcp/main/src/redshift-mcp-server/README.md (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datamcpservers.com/glossary/human-confirmation/
