x-twitter.user_timeline
Fetch a user's recent X (Twitter) posts, pinned tweet, and profile summary. 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 timeline entries with tweet text, engagement counts, media, quo...
This record as markdown: /tools/io-github-vee3io-vee3/x-twitter.user-timeline.md
What x-twitter.user_timeline does on Vee3
AI agents use x-twitter.user_timeline 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 |
|---|---|---|---|
cursor | object | — | Pagination cursor from a previous response next_cursor field. |
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.
Why x-twitter.user_timeline is rated Medium
An AI agent can call x-twitter.user_timeline 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
The rule that runs x-twitter.user_timeline 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_timeline, this is the rule to start with:
x-twitter.user_timeline 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every x-twitter.user_timeline call is checked against it from then on.
Questions about x-twitter.user_timeline
Fetch a user's recent X (Twitter) posts, pinned tweet, and profile summary. 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 timeline entries with tweet text, engagement counts, media, quoted tweets, and author info. Use cursor from next_cursor to fetch the next page. Cost = 4 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.
x-twitter.user_timeline accepts 3 parameters: cursor, rest_id, user_name. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for x-twitter.user_timeline: 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.
x-twitter.user_timeline is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the x-twitter.user_timeline 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.
Set action: deny in the PolicyLayer policy for x-twitter.user_timeline. 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.
x-twitter.user_timeline 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.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue