Publish a text post to the default channel or a provided chat_id. reply_markup can be inline_keyboard dict.
AI agents use publish_post to create or update resources in SergeyKrin9/mcp Servers — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SergeyKrin9/mcp Servers environment.
This tool creates and publishes new content to social media/messaging platforms, which is reversible via deletion but represents a Write operation with moderate blast radius. Publishing unsolicited messages, spam, or misleading content via an AI agent could cause reputational harm.
From the tool's definition Tool name 'publish_post' and description 'Publish a text post to the default channel or a provided chat_id' indicates creation of new content in external systems (Telegram/VK). The reply_markup parameter shows it modifies message structure.
Attacks that exploit this kind of access
Publish a text post to the default channel or a provided chat_id. reply_markup can be inline_keyboard dict. It is categorised as a Write tool in the SergeyKrin9/mcp Servers MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SergeyKrin9/mcp Servers MCP server in PolicyLayer and add a rule for 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 SergeyKrin9/mcp Servers. Nothing to install.
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 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 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.
publish_post is provided by the SergeyKrin9/mcp Servers MCP server (sergeykrin9/mcp-servers). 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 →