|
Installieren Free USD Wechselkurse!
Installieren Free Währungsrechner!
Deprecated: Creation of dynamic property lastRSS::$cache_dir is deprecated in /www/wwwroot/exchangerateeuro.org/00rss.php on line 45
Deprecated: Creation of dynamic property lastRSS::$cache_sqlite is deprecated in /www/wwwroot/exchangerateeuro.org/00rss.php on line 46
Deprecated: Creation of dynamic property lastRSS::$cache_time is deprecated in /www/wwwroot/exchangerateeuro.org/00rss.php on line 47
Deprecated: Creation of dynamic property lastRSS::$rsscp is deprecated in /www/wwwroot/exchangerateeuro.org/lastRSS.php on line 234
- When Neither Side Confirms: Destructive Tool Approval Across MCP . . .
LLM agents call tools that delete data or move money through the Model Context Protocol (MCP) The specification asks for a human who can deny tool calls but splits the mechanism between the server, which can annotate a tool or ask the user through the host (elicitation), and the host application, which decides whether to prompt We measure both sides from source code In a 1,000-repository
- When Neither Side Confirms: Destructive Tool Approval Across MCP . . .
The MCP specification says there “SHOULD always be a human in the loop with the ability to deny tool invocations” (Model Context Protocol, 2026) It asks applications to present confirma-tion prompts but mandates no enforcement, and it does not say whether a server should proceed or refuse when the host cannot ask Practitioners dif-fer: the confirmation rules of a Kubernetes server
- Recommended Control: Client-Side Tool Risk Gating for MCP Hosts
Overview Client-side tool risk gating is a host-side control pattern: the MCP host (client) vets every tool before the model can see or call it, using only what the existing protocol already exposes It requires no cooperation from upstream servers, no new protocol fields, and no signing infrastructure, so it can be deployed today against any unmodified MCP server It is complementary to
- Human-in-the-Loop Approval - Spring AI Playground
How Spring AI Playground gates tool calls behind human approval - one per-tool flag enforced at the caller's entry point: chat dialog or MCP elicitation, fail-safe
- Human approval for MCP tool calls is the real control boundary
TL;DR: Human-in-the-loop approval for MCP tool calls separates permitted action from acceptable action, according to TruFoundry ’s comparison of gateway approaches Without a stateful approval step, enterprises risk turning valid agent actions into irreversible incidents because conventional IAM controls cannot judge consequence in context
- The Human Gate: Designing MCP Tool Approvals at the Gateway Boundary
The engineering value is not that MCP standardized approval—it did not—but that approval can be enforced at a shared tool boundary, scoped to identity and tool, and correlated with the execution path without turning a transient human decision into permanent authorization policy
- MCP tool approvals at the gateway boundary: what changes
TL;DR: MCP tool approvals are an implementation-layer control, not a protocol-standard approval state, according to TruFoundry 's analysis, and they work by holding matched tool calls at the gateway while returning a pending result with approval metadata The governance challenge is that human review, requester scoping, and validity windows must be enforced deliberately or they collapse into
- how could we introduce a human-in-the-loop step for double confirm and . . .
Currently, human validation is done on the client side Before you send a tool-execution request, you may want to run this by a human in your application However, you bring an interesting point about servers potentially being able to trigger this as well -- essentially adding MCP client capability to handle human input requests from the server (i e server -> client -> human flow), similar to
|
|
Andere Währung Tool:
Warning: include_once(../cacheforex2/de/00curr_w2_de.html): Failed to open stream: No such file or directory in /www/wwwroot/exchangerateeuro.org/review.php on line 209
Warning: include_once(): Failed opening '../cacheforex2/de/00curr_w2_de.html' for inclusion (include_path='.:') in /www/wwwroot/exchangerateeuro.org/review.php on line 209
|