x-twitter.repost_post
Repost a post for a connected X account. Call x-twitter.connected_accounts first. Pass user_id or user_name to target a specific account, or omit both to use the default account. Returns the reposted post_id and retweeted status. Cost = 75 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/x-twitter.repost-post.md
What x-twitter.repost_post does on Vee3
AI agents use x-twitter.repost_post 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 |
|---|---|---|---|
post_id | string | Yes | Numeric id of the post to repost. |
user_id | object | — | Numeric X user id from x-twitter.connected_accounts. Pass user_id or user_name to target a specific account, not both. Omit both to use the default account. |
user_name | object | — | X handle from x-twitter.connected_accounts, with or without a leading @. Pass user_id or user_name to target a specific account, not both. Omit both to use the |
Parameters from the server's own tool schema.
Why x-twitter.repost_post is rated Medium
Reposts/retweets content publicly on behalf of a connected X (Twitter) account. This is a Write operation as it creates a new association (repost) on the platform. It is reversible (can be unreposted), but misuse could spread misinformation or spam at scale, giving it high severity since it acts on real social media accounts and publishes content publicly.
From the tool's definition Repost a post for a connected X account
Attacks that exploit this kind of access
The rule that runs x-twitter.repost_post 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.repost_post, this is the rule to start with:
x-twitter.repost_post 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.repost_post call is checked against it from then on.
Questions about x-twitter.repost_post
Repost a post for a connected X account. Call x-twitter.connected_accounts first. Pass user_id or user_name to target a specific account, or omit both to use the default account. Returns the reposted post_id and retweeted status. Cost = 75 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.repost_post accepts 3 parameters: post_id, user_id, user_name. Required: post_id. 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.repost_post: 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.repost_post 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.repost_post 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.repost_post. 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.repost_post 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