x_publish_post
Publish a post to the connected X (Twitter) account with optional media. Text can include mentions, hashtags, and URLs. Media files are uploaded via v2 chunked upload. Returns tweet_id and URL.
This record as markdown: /tools/io-github-saloprj-dialogbrain/x-publish-post.md
What x_publish_post does on Dialogbrain
AI agents use x_publish_post to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | Post text (required). X enforces per-account character limits. |
account_id | string | — | X account: numeric channel account ID or @handle (optional; defaults to workspace's sole X account). |
media_file_ids | array | — | DialogBrain file IDs to attach (optional, max 4 per post). |
Parameters from the server's own tool schema.
Why x_publish_post is rated Medium
This tool creates new data (social media posts) on X/Twitter irreversibly once published, but does not delete, destroy financial resources, or execute arbitrary code. The primary action is creation/publication of content, fitting the Write category.
From the tool's definition Tool description states 'Publish a post to the connected X (Twitter) account' and 'Returns tweet_id and URL', indicating creation of new content on an external platform.
Attacks that exploit this kind of access
The rule that runs x_publish_post safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For x_publish_post, this is the rule to start with:
x_publish_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 Dialogbrain, apply this rule, and every x_publish_post call is checked against it from then on.
Questions about x_publish_post
Publish a post to the connected X (Twitter) account with optional media. Text can include mentions, hashtags, and URLs. Media files are uploaded via v2 chunked upload. Returns tweet_id and URL. It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
x_publish_post accepts 3 parameters: text, account_id, media_file_ids. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for x_publish_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 Dialogbrain. Nothing to install.
x_publish_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_publish_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_publish_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_publish_post is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue