Unverified50% confidenceTradeoffExact time
Parameters themselves are part of the permission surface: adding a path parameter to a file-reading tool is equivalent to expanding permission from a certain directory to arbitrary paths (path traversal risk); adding cc or bcc to send-email is equivalent to expanding the outbound scope. Therefore scope review should be conducted continuously as tool schemas change.
1
Sources
50%
Confidence
Long-term
Relevance
10/15/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedCSL-Core sets per-call limits and approval thresholds for finance-related tools, applies a whitelist mechanism for tools that execute commands, and restricts write operations to a defined folder scope.62% similarUnverifiedFileRouter's rule system allows users to set fine-grained opening logic for any file type, determining which app to open based on conditions such as file path, extension, and modifier key state.62% similarUnverifiedA file-read tool with path traversal, a URL fetch tool without target filtering (an SSRF vector), and a Shell execution tool without an allowlist (arbitrary code execution) are all exploitable items for indirect prompt injection.61% similarUnverifiedThe pattern of writing constraints as pre-commit hooks can be transferred to many scenarios, such as enforcing the use of a unified logging module, prohibiting direct reading of environment variables, and prohibiting the introduction of certain types of dependencies in specific directories, as long as the constraints can be written as static checks.60% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1035685API
curl https://kongchang.com/api/v1/knowledge/claims/1035685MCP
get_claim(id=1035685)