x-twitter.user_info

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

Medium RISK CLASS

Category Write

Parameters 20 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What x-twitter.user_info does on Vee3

AI agents use x-twitter.user_info to create or update resources in Vee3, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vee3 environment.

Parameter	Type	Required	Description
`rest_id`	object	—	Numeric X user id (rest_id). When provided, user_name is ignored.
`user_name`	object	—	X handle without the leading @ (for example elonmusk). Required when rest_id is omitted.

Parameters from the server's own tool schema.

RISK

Why x-twitter.user_info is rated Medium

An AI agent can call x-twitter.user_info faster than any human can review: one bad instruction and it creates or modifies resources in Vee3 by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs x-twitter.user_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.user_info, this is the rule to start with:

x-twitter.user_info Rate-limited

x-twitter.user_info stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "x-twitter.user_info": {
      "limits": [
        {
          "counter": "x-twitter.user_info_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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.user_info call is checked against it from then on.

FAQ

Questions about x-twitter.user_info

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

Fetch public profile metadata for an X (Twitter) user. Provide user_name (handle without @) or rest_id (numeric user id). At least one is required. When rest_id is set, it takes precedence over user_name. Returns display name, bio, follower counts, verification flags, avatar URLs, and related profile fields. Cost = 2 tokens. It is categorised as a Write tool in the Vee3 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does x-twitter.user_info accept? +

x-twitter.user_info accepts 2 parameters: rest_id, user_name. The full parameter table on this page comes from the server's own tool schema.

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

Register the Vee3 MCP server in PolicyLayer and add a rule for x-twitter.user_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.user_info? +

x-twitter.user_info is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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

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

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

x-twitter.user_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

Govern customer-ops agents →Argument validation →Scoped token →