Immediately publish a draft or scheduled post, bypassing any scheduled time. Returns the post in its current state — actual platform delivery is asynchronous, so the response status may still be Scheduled until the worker picks it up. Use get_post to check progress.
AI agents invoke publish_post_now to trigger actions in Viraly MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation — publishing content to a social media platform — immediately and bypasses scheduling logic. It is an irreversible action in the sense that once published, content is live (though it could potentially be deleted later). It fits Execute best because it triggers an external platform operation whose effects are asynchronous and depend on state.
From the tool's definition Immediately publish a draft or scheduled post, bypassing any scheduled time
Attacks that exploit this kind of access
Immediately publish a draft or scheduled post, bypassing any scheduled time. Returns the post in its current state — actual platform delivery is asynchronous, so the response status may still be Scheduled until the worker picks it up. Use get_post to check progress. It is categorised as a Execute tool in the Viraly MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Viraly MCP Server MCP server in PolicyLayer and add a rule for publish_post_now: 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 Viraly MCP Server. Nothing to install.
publish_post_now is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the publish_post_now 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_post_now. 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_post_now is provided by the Viraly MCP Server MCP server (viraly-io/viraly-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →