getTweet

THE RISK

Low Risk

Why getTweet needs a policy

This tool retrieves a single tweet's content by its identifier. It performs a query operation that returns data without creating, modifying, deleting, or executing any actions.

From the tool's definition Tool name 'getTweet' and description 'Get a specific tweet by ID' indicate retrieval of existing data with no modification or side effects.

Documented attack patterns abuse exactly the kind of access getTweet gives an agent:

POLICY

How to control getTweet

PolicyLayer is an MCP gateway — it sits between your AI agents and Twitter Client MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for getTweet:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getTweet": {}
  }
}

getTweet is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Twitter Client MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Twitter Client MCP tools

Write followUser Follow a Twitter user Write likeTweet Like a tweet Write retweet Retweet a tweet Write sendTweet Post a new tweet with optional media and/or as a reply Write sendTweetWithMedia Post a new tweet with attached media (images/videos). Twitter limitations: max 4 images OR Write uploadMedia Prepare media (image/video) for posting to Twitter Read getConversationThread Get a tweet conversation thread including the parent tweet Read getListTweets Get tweets from a Twitter list

All 20 Twitter Client MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about getTweet

What does the getTweet tool do? +

Get a specific tweet by ID. It is categorised as a Read tool in the Twitter Client MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getTweet? +

Register the Twitter Client MCP server in PolicyLayer and add a rule for getTweet: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Twitter Client MCP. Nothing to install.

What risk level is getTweet? +

getTweet is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getTweet? +

Yes. Add a rate_limit block to the getTweet rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block getTweet completely? +

Set action: deny in the PolicyLayer policy for getTweet. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides getTweet? +

getTweet is provided by the Twitter Client MCP server (mzkrasner/twitter-client-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Twitter Client MCP tool call.

Start from Twitter Client MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →