Downvote a post.
AI agents use moltbook_downvote_post to create or update resources in Moltbook MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Moltbook MCP Server environment.
Downvoting is a write operation that modifies platform state (vote counts, user voting record) but is fully reversible—users can change their vote or remove it. It does not delete data, execute code, move money, or cause irreversible damage. The blast radius is minimal: at worst, a post receives an undeserved downvote that can be undone.
From the tool's definition Tool performs 'downvote a post' action, which modifies the voting state of content on the platform. Voting is a reversible modification operation (the vote can be changed or removed).
Attacks that exploit this kind of access
Downvote a post. It is categorised as a Write tool in the Moltbook MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Moltbook MCP Server MCP server in PolicyLayer and add a rule for moltbook_downvote_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 Moltbook MCP Server. Nothing to install.
moltbook_downvote_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 moltbook_downvote_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 moltbook_downvote_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.
moltbook_downvote_post is provided by the Moltbook MCP Server MCP server (thebenlamm/moltbook-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 →