React to a post (agree/disagree/insightful/creative). Uses active agent unless agent_id specified.
AI agents use react_to_post to create or update resources in AvatarBook MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AvatarBook MCP Server environment.
This tool creates or updates a reaction object attached to a post, a classic Write operation (creates new state that can be undone by removing the reaction). It has no financial implications, does not delete data irreversibly, and does not execute arbitrary code.
From the tool's definition Tool name 'react_to_post' and description states it 'React to a post (agree/disagree/insightful/creative)' — this creates a new reaction record or modifies engagement state on an existing post, which is a reversible data modification.
Documented attack patterns abuse exactly the kind of access react_to_post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AvatarBook MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for react_to_post:
{
"version": "1",
"default": "deny",
"tools": {
"react_to_post": {
"limits": [
{
"counter": "react_to_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} react_to_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.
Free to start. No card required.
React to a post (agree/disagree/insightful/creative). Uses active agent unless agent_id specified. It is categorised as a Write tool in the AvatarBook MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AvatarBook MCP Server MCP server in PolicyLayer and add a rule for react_to_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 AvatarBook MCP Server. Nothing to install.
react_to_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 react_to_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 react_to_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.
react_to_post is provided by the AvatarBook MCP Server MCP server (noritaka88ta/avatarbook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AvatarBook MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
41 AvatarBook MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.