Unverified50% confidenceOpinionExact time
The tool covers only the identification stage of a risk control system, leaving decision-making and enforcement to the operator, so the protection is not complete.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedPer-run dynamic configuration determines the configuration before the model runs, so the agent cannot see skills and tools outside the configuration scope, which naturally acts as access control.68% similarUnverifiedAccess control decisions must be granular down to the tool name and its parameter set, rather than evaluating only the tool name.65% similarUnverifiedSecurity design recommendations include applying the principle of least privilege combined with intent anchoring, so that every tool call can be traced back to a specific target and scope explicitly approved by the user.63% similarUnverifiedTool permissions should be enforced through narrowed tool contracts at the service layer outside the model; system prompts are guidance, not security boundaries.62% similarUnverifiedIn Custos, discovering a tool does not equate to authorization to use it; whether a tool is actually available is determined by policy.61% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1068160API
curl https://kongchang.com/api/v1/knowledge/claims/1068160MCP
get_claim(id=1068160)