query_logs — decoy.day honeypot MCP Tool Read-only
query_logs
(query logs) is one of 17 tools on the
decoy.day honeypot
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call query_logs from your client
- Claude Code decoy.day honeypot query_logs run in your project directory
- Claude Desktop decoy.day honeypot query_logs ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor decoy.day honeypot query_logs ~/.cursor/mcp.json
- VS Code decoy.day honeypot query_logs .vscode/mcp.json
- Zed decoy.day honeypot query_logs ~/.config/zed/settings.json
- Windsurf decoy.day honeypot query_logs ~/.codeium/windsurf/mcp_config.json
- Cline decoy.day honeypot query_logs ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI decoy.day honeypot query_logs ~/.gemini/settings.json
- Grok decoy.day honeypot query_logs .mcp.json (in your project root)
- ChatGPT decoy.day honeypot query_logs Settings → Connectors → Advanced → Developer mode
- Claude.ai decoy.day honeypot query_logs Settings → Connectors → Add custom connector
- LangChain decoy.day honeypot query_logs pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http honeypot https://mcp.decoy.day/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.