T08 · Insecure Dependencies
- Location
SKILL.md:31- Finding
Unpinned Third-Party Plugin Is Installed and Added to the Agent Tool Allowlist
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent Stack Exchange integration, but it asks users to install and allowlist an external plugin while exposing private OAuth-backed account data and token-inspection tools with weak consent guidance.
Install only if you trust ClawLink and are comfortable granting OAuth-backed access to Stack Exchange account data. Prefer using public search tools without connecting OAuth when possible, avoid granting read_inbox unless you need inbox or notification features, and treat token-inspection output as sensitive. Verify the plugin package/version before allowlisting it in OpenClaw.
SKILL.md:31Unpinned Third-Party Plugin Is Installed and Added to the Agent Tool Allowlist
SKILL.md:192Sensitive OAuth-Backed Account Capabilities Exceed the Needs of Public Q&A Retrieval
A tool explicitly described as able to 'verify and inspect OAuth access tokens' creates a credential-access surface inside the skill. Even if intended for troubleshooting, exposing token inspection capability to the agent increases the risk of secret disclosure, token mishandling, or downstream abuse if outputs are logged, summarized, or shown to unauthorized users.
|------|-------------|------|
| `stack_exchange_create_filter` | Create a custom response filter | Write |
| `stack_exchange_get_filters_by_ids` | Retrieve filter field definitions | Read |
| `stack_exchange_get_access_tokens` | Verify and inspect OAuth access tokens | Read |
## Code Examples
The statement that read operations 'require no confirmation' encourages autonomous execution based solely on the skill's self-assessment of safety. In this skill, many 'read' tools can access authenticated user data such as inbox, notifications, reputation history, associated accounts, and token inspection, so removing confirmation can expose sensitive information without explicit user consent.
## Security & Permissions
- **Read** operations are safe and require no confirmation. All Stack Exchange tools in this integration are read-only or create filters.
- **Write** operations are limited to creating custom filters, which are safe helper objects.
- The Stack Exchange API has a daily request quota. Monitor `quota_remaining` in responses.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## Resources
- Stack Exchange API Docs: https://api.stackexchange.com/docs
- ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=stack-exchange
- ClawLink Docs: https://docs.claw-link.dev/openclaw
No suspicious patterns detected.