publish_social_post
Publish a post (post_id from list_social_posts) on X on behalf of the brand: a post waiting for approval goes out at its proposed time (or now, if that time has passed); a draft goes out now. Requires the separate social:publish permission. X charges the publisher's X account.
This record as markdown: /tools/com-idosgames-platform/publish-social-post.md
What publish_social_post does on iDos Games
AI agents use publish_social_post to create or update resources in iDos Games, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your iDos Games environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
post_id | string | Yes | Post id. |
title_id | string | Yes | TitleID. |
Parameters from the server's own tool schema.
Why publish_social_post is rated Medium
An AI agent can call publish_social_post faster than any human can review: one bad instruction and it creates or modifies resources in iDos Games by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs publish_social_post safely
PolicyLayer is an MCP gateway: it sits between your AI agents and iDos Games, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For publish_social_post, this is the rule to start with:
publish_social_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 iDos Games, apply this rule, and every publish_social_post call is checked against it from then on.
Questions about publish_social_post
Publish a post (post_id from list_social_posts) on X on behalf of the brand: a post waiting for approval goes out at its proposed time (or now, if that time has passed); a draft goes out now. Requires the separate social:publish permission. X charges the publisher's X account. It is categorised as a Write tool in the iDos Games MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
publish_social_post accepts 2 parameters: post_id, title_id. Required: post_id, title_id. The full parameter table on this page comes from the server's own tool schema.
Register the iDos Games MCP server in PolicyLayer and add a rule for publish_social_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 iDos Games. Nothing to install.
publish_social_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 publish_social_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 publish_social_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.
publish_social_post is provided by the iDos Games MCP server (https://site.idosgames.com/api/v2/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on iDos Games, and thousands of servers like it.
This server
Across the catalogue