x-twitter.tweet_info

Fetch metadata for a single public X (Twitter) post by its numeric tweet id. Returns tweet text, engagement counts (likes, retweets, replies, quotes, bookmarks), language, conversation id, author profile summary, and attached media when present. Cost = 2 tokens.

SERVERVee3 SOURCEhttps://mcp.vee3.io/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vee3io-vee3/x-twitter.tweet-info.md

WHAT IT DOES

What x-twitter.tweet_info does on Vee3

AI agents call x-twitter.tweet_info to retrieve information from Vee3 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`id`	string	Yes	Numeric tweet id.

Parameters from the server's own tool schema.

RISK

Why x-twitter.tweet_info is rated Low

Retrieves public tweet metadata and engagement counts without modifying data or side effects.

From the tool's definition Fetch metadata for a single public X post by numeric tweet id.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs x-twitter.tweet_info safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For x-twitter.tweet_info, this is the rule to start with:

x-twitter.tweet_info Allowed

x-twitter.tweet_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "x-twitter.tweet_info": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every x-twitter.tweet_info call is checked against it from then on.

FAQ

Questions about x-twitter.tweet_info

What does the x-twitter.tweet_info tool do? +

What parameters does x-twitter.tweet_info accept? +

x-twitter.tweet_info accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on x-twitter.tweet_info? +

Register the Vee3 MCP server in PolicyLayer and add a rule for x-twitter.tweet_info: 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 Vee3. Nothing to install.

What risk level is x-twitter.tweet_info? +

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

Can I rate-limit x-twitter.tweet_info? +

Yes. Add a rate_limit block to the x-twitter.tweet_info 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 x-twitter.tweet_info completely? +

Set action: deny in the PolicyLayer policy for x-twitter.tweet_info. 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 x-twitter.tweet_info? +

x-twitter.tweet_info is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vee3, and thousands of servers like it.

This server

All 249 Vee3 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →