Unverified50% confidenceDecision RuleExact time
The instructor recommends enforcing server identity at the registry level (registry-only) and not using allow all, because allow all makes it impossible to trace which tools the Agent has called.
1
Sources
50%
Confidence
Long-term
Relevance
10/8/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedSecure design should approve read-only issue queries without enabling repository write permissions, and servers should not be allowed to modify tools, databases, or applications.67% similarUnverifiedThe principle of least privilege recommends creating dedicated service accounts for agents, granting only the necessary read-only permissions in the Graph API (such as Sites.Read.All), with write permissions subject to separate approval and logged.67% similarUnverifiedWhen code only verifies that a user is logged in without verifying whether the user is authorized to invoke a specific tool, it is equivalent to exposing the entire toolset to any caller holding a valid token.64% similarUnverifiedDelegated authentication ensures that the agent's access scope for semantic models and reports, as well as RLS and OLS restrictions, is consistent with the logged-in user and cannot bypass security policies.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/987530API
curl https://kongchang.com/api/v1/knowledge/claims/987530MCP
get_claim(id=987530)