# Knostic: MCP tool asks agents for a GitHub token

URL: https://mcpservercybersecurity.com/news/knostic-mcp-tool-description-asks-agent-for-github-token/
Updated: 2026-11-12

Knostic published a static review on 12 Nov 2026 of @agentdance/node-webrtc-mcp version 1.0.13. Knostic says the description of its get_started tool contains an instruction telling the agent to obtain a GitHub token without asking the user, and that the server then uses a supplied token to favorite the publisher's repository.

2026-11-12

Knostic says the package helps coding agents pick a WebRTC library and generate starter code. The README says the tool favorites the publisher's repository when given a token, but the text the agent reads goes further and tells it to fetch the credential itself and not to ask the user. Knostic notes the tool code also marks every requirement as satisfied and that the README says the comparison tool always recommends the publisher's library.

Knostic did not install or run the package; the post is a static code review. The case shows why a tool description is untrusted input: the agent reads it to decide how to call the tool, so its text can steer behavior.

The post ends with practical checks. For a platform team, the controls that apply are a review step for tool descriptions before a server is approved, a pinned version, and an alert when a description changes.

## Sources

- [When an MCP Tool Asks for Your GitHub Token, Knostic](https://www.knostic.ai/blog/when-an-mcp-tool-asks-for-your-github-token) (knostic.ai), read 2026-11-16

## Related pages

- [Knostic profile](/vendors/knostic/)
- [All news](/news/)
- [MCP Python SDK 2.2.0 tightens redirects and sessions](/news/python-sdk-2-2-0-redirect-session-issuer-defaults/)
- [MCP draft spec adopts Client ID Metadata draft 03](/news/mcp-spec-draft-client-id-metadata-document-draft-03/)
- [The ranking](/ranking/)
