x-twitter.connected_accounts
List X (Twitter) accounts connected to the authenticated Vee3 account for write capabilities. Returns user_id, user_name, display name, avatar URL, and whether each account is the default. Use user_id or user_name on future write calls, or omit both to use the default account. If accounts is empt...
This record as markdown: /tools/io-github-vee3io-vee3/x-twitter.connected-accounts.md
What x-twitter.connected_accounts does on Vee3
AI agents call x-twitter.connected_accounts 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.
Why x-twitter.connected_accounts is rated Low
This tool performs a read-only listing of connected accounts. It returns informational metadata and does not create, modify, delete, or trigger any external operations. Misuse potential is low since it only exposes account identifiers already known to the authenticated user.
From the tool's definition 'List X (Twitter) accounts connected to the authenticated Vee3 account' and 'Cost = 0 tokens' — the tool only retrieves account metadata (user_id, user_name, display name, avatar URL, default flag) with no side effects.
Attacks that exploit this kind of access
The rule that runs x-twitter.connected_accounts 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.connected_accounts, this is the rule to start with:
x-twitter.connected_accounts is read-only, so it stays allowed. 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.connected_accounts call is checked against it from then on.
Questions about x-twitter.connected_accounts
List X (Twitter) accounts connected to the authenticated Vee3 account for write capabilities. Returns user_id, user_name, display name, avatar URL, and whether each account is the default. Use user_id or user_name on future write calls, or omit both to use the default account. If accounts is empty, the user must connect an X account at https://vee3.io/dashboard/connections before write capabilities work. Agents cannot complete OAuth; ask the user to connect, then call this tool again. Cost = 0 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
Register the Vee3 MCP server in PolicyLayer and add a rule for x-twitter.connected_accounts: 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.connected_accounts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the x-twitter.connected_accounts 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.connected_accounts. 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.connected_accounts 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