# get_twitter_tweet_by_id

A read tool on the Twitter MCP Server MCP server.

Agent View of the PolicyLayer registry record for `get_twitter_tweet_by_id`. HTML page: https://policylayer.com/tools/6551team-opentwitter-mcp/get-twitter-tweet-by-id

## Facts

- Tool: `get_twitter_tweet_by_id`
- Server: Twitter MCP Server (`6551team/opentwitter-mcp`) — https://policylayer.com/tools/6551team-opentwitter-mcp.md
- Homepage: https://github.com/6551Team/opentwitter-mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_twitter_tweet_by_id",
    "arguments": {}
  }
}
```

## Why get_twitter_tweet_by_id is rated Low

This tool retrieves a single tweet by its ID without altering any data. The capability to access tweets (including potentially sensitive content given the server's ability to track KOL activity and access deleted tweets) warrants medium severity due to potential privacy and information disclosure risks, but it remains fundamentally a Read operation with no side effects.

From the tool's own definition: "Tool name 'get_twitter_tweet_by_id' clearly indicates a retrieval operation. Server description confirms it 'retrieve[s] user profiles, search tweets, and track engagement metrics' with no mention of modifications."

## Use case

AI agents call get_twitter_tweet_by_id to retrieve information from Twitter MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Twitter MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_twitter_tweet_by_id": {}
  }
}
```

## Other tools on Twitter MCP Server (16)

- `delete_twitter_watch` — Destructive — https://policylayer.com/tools/6551team-opentwitter-mcp/delete-twitter-watch.md
- `get_meme_activity` — Read — https://policylayer.com/tools/6551team-opentwitter-mcp/get-meme-activity.md
- `get_meme_token_evidence` — Read — https://policylayer.com/tools/6551team-opentwitter-mcp/get-meme-token-evidence.md
- `get_twitter_article_by_id` — Read — https://policylayer.com/tools/6551team-opentwitter-mcp/get-twitter-article-by-id.md
- `get_twitter_deleted_tweets` — Read — https://policylayer.com/tools/6551team-opentwitter-mcp/get-twitter-deleted-tweets.md
- `get_twitter_follower_events` — Read — https://policylayer.com/tools/6551team-opentwitter-mcp/get-twitter-follower-events.md
- `get_twitter_kol_followers` — Read — https://policylayer.com/tools/6551team-opentwitter-mcp/get-twitter-kol-followers.md
- `get_twitter_quote_tweets_by_id` — Read — https://policylayer.com/tools/6551team-opentwitter-mcp/get-twitter-quote-tweets-by-id.md
- `get_twitter_retweet_users_by_id` — Read — https://policylayer.com/tools/6551team-opentwitter-mcp/get-twitter-retweet-users-by-id.md
- `get_twitter_user` — Read — https://policylayer.com/tools/6551team-opentwitter-mcp/get-twitter-user.md
- `get_twitter_user_by_id` — Read — https://policylayer.com/tools/6551team-opentwitter-mcp/get-twitter-user-by-id.md
- `get_twitter_user_tweets` — Read — https://policylayer.com/tools/6551team-opentwitter-mcp/get-twitter-user-tweets.md
- `get_twitter_watch` — Read — https://policylayer.com/tools/6551team-opentwitter-mcp/get-twitter-watch.md
- `search_twitter` — Read — https://policylayer.com/tools/6551team-opentwitter-mcp/search-twitter.md
- `search_twitter_advanced` — Read — https://policylayer.com/tools/6551team-opentwitter-mcp/search-twitter-advanced.md
- `add_twitter_watch` — Write — https://policylayer.com/tools/6551team-opentwitter-mcp/add-twitter-watch.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=6551team-opentwitter-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/6551team-opentwitter-mcp