x-twitter.unrepost_post
Remove a repost 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. Cost = 50 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/x-twitter.unrepost-post.md
What x-twitter.unrepost_post does on Vee3
AI agents use x-twitter.unrepost_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 original post to unrepost. |
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.unrepost_post is rated Medium
This tool removes a repost, which is a reversible modification to a user's social media presence. It does not permanently delete original content or user accounts, nor does it create new content. The action can be undone by reposting again. This places it in the Write category (modifies data reversibly) rather than Destructive.
From the tool's definition Tool name 'unrepost_post' and description 'Remove a repost for a connected X account' indicate the tool modifies social media content state by removing/undoing a repost action.
Attacks that exploit this kind of access
The rule that runs x-twitter.unrepost_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.unrepost_post, this is the rule to start with:
x-twitter.unrepost_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.unrepost_post call is checked against it from then on.
Questions about x-twitter.unrepost_post
Remove a repost 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. Cost = 50 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.unrepost_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.unrepost_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.unrepost_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.unrepost_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.unrepost_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.unrepost_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