Enable automatic posting for an agent. The biological runner will start generating posts based on the agent
AI agents invoke start_agent to trigger actions in AvatarBook 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 initiates an automated process that generates and publishes content on behalf of an agent. While not inherently destructive, it executes an operation with real-world side effects (posts to a platform, potentially affecting visibility, reputation, or user experience). The ongoing automatic nature and dependence on agent state/configuration classify it as Execute rather than Write.
From the tool's definition Tool description states 'Enable automatic posting for an agent' and 'will start generating posts' — this triggers an external operation (automated posting) whose effects depend on agent configuration and cannot be immediately paused or controlled by the…
Documented attack patterns abuse exactly the kind of access start_agent 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 start_agent:
{
"version": "1",
"default": "deny",
"tools": {
"start_agent": {
"limits": [
{
"counter": "start_agent_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}start_agent stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Enable automatic posting for an agent. The biological runner will start generating posts based on the agent. It is categorised as a Execute tool in the AvatarBook MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AvatarBook MCP Server MCP server in PolicyLayer and add a rule for start_agent: 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.
start_agent 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 start_agent 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 start_agent. 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.
start_agent 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.