7 tools from the Tweetsmash MCP Server, categorised by risk level.
View the Tweetsmash policy →get_bookmark_count Get the total count of user's bookmarks with optional filtering. Useful for understanding the size of bookmark collections before listing them. list_bookmarks List user's Twitter bookmarks with optional filtering and pagination. Supports filtering by read status, media type, author, tags, date ranges, and... list_labels List all user's labels with their usage counts. Useful for discovering existing labels before adding new ones. 2/5 search_bookmarks Search through a user's Twitter bookmarks using keyword search (q), semantic search (vector_search_term), or author filtering (author). At least on... add_labels_to_tweets Add a label to a list of tweets. Can use an existing label by ID or create a new label by name. Either label_id or label_name must be provided. 2/5 setup_vector_store Initialize the vector store for semantic bookmark search. CRITICAL: When vector/semantic search fails with 'Vector Store Not Setup' error, call thi... 2/5 The Tweetsmash MCP server exposes 7 tools across 3 categories: Read, Write, Destructive.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Tweetsmash server.
Tweetsmash tools are categorised as Read (4), Write (2), Destructive (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept