0 Plugins should be inspected and tested thoroughly to ensure adequate validation.  Use Static Application Security Testing (SAST) scans as well as Dynamic and Interactive application testing (DAST, IAST) in development pipelines Plugins should be designed to minimize the impact of any insecure input parameter exploitation following the OWASP ASVS Access Control Guidelines.  This includes least-privilege access control, exposing as little functionality as possible while still performing its desired function Plugins should use appropriate authentication identities, such as OAuth2, to apply effective authorization and access control.  Additionally, API Keys should be used to provide context for custom authorization decisions which reflect the plugin route rather than the default interactive user Require manual user authorization and confirmation of any action taken by sensitive plugins Plugins are, typically, REST APIs, so developers should apply the recommendations found in OWASP Top 10 API Security Risks – 2023 to minimize generic vulnerabilities Example Attack Scenarios A plugin accepts a base URL and instructs the LLM to combine the URL with a query to obtain weather forecasts which are included in handling the user request.  A malicious user can craft a request such that the URL points to a domain they control, which allows them to inject their own content into the LLM system via their domain A plugin accepts a free-form input into a single field that it does not validate