Unverified50% confidenceFactExact time
The MCP host can be configured to require approval before executing OutSystems tools that modify the tenant, so confirmation does not depend entirely on whether the Agent follows instructions.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/28/2026
First Seen
Valid until: 1/26/2027
Sources
Related Entities
Related Claims
VerifiedThe MCP specification requires hosts to ask for user confirmation before running any tool, mandating that a human-in-the-loop step be retained.72% similarUnverifiedA mature MCP gateway needs a built-in user consent flow capable of triggering confirmation before an Agent performs high-risk actions, recording user authorization status, and updating permissions when authorization changes71% similarUnverifiedWhen using the Fabric Core MCP Server, it is recommended to use least-privilege identities, keep client approval settings enabled, review tool calls before changes are executed, and not point agents holding tenant administrator accounts directly at production environments.69% similarUnverifiedDecision recommendation: use MCP when cross-account, cross-service permission isolation and on-demand authorization are needed; if you simply want to expose a set of internal actions to the model, just write instructions to provide a program interface directly.68% similarUnverifiedWhen evaluating an MCP integration, one must confirm that permission checks occur on the server side in the context of each retrieval request, rather than relying solely on identity verification at connection initialization.68% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1106801API
curl https://kongchang.com/api/v1/knowledge/claims/1106801MCP
get_claim(id=1106801)