Post a message to the Stability blockchain
AI agents use post_message to create or update resources in Stability MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stability MCP Server environment.
This tool creates or appends data (a message) to the Stability blockchain. While it modifies state, it is reversible or recoverable in principle (messages can be deleted or overwritten in most blockchain designs), and it does not irreversibly destroy data or move financial assets. The 'post' verb confirms it is a Write operation rather than Read.
From the tool's definition Tool name 'post_message' and description 'Post a message to the Stability blockchain' indicate a data creation operation that modifies blockchain state.
Attacks that exploit this kind of access
Post a message to the Stability blockchain. It is categorised as a Write tool in the Stability MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Stability MCP Server MCP server in PolicyLayer and add a rule for post_message: 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 Stability MCP Server. Nothing to install.
post_message 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 post_message 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 post_message. 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.
post_message is provided by the Stability MCP Server MCP server (nuljui/stbl-mcp). 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 →