Start a new conversation with an agent. Provide your message and the agent will respond.
AI agents invoke start_agent_conversation to trigger actions in Automagik Tools. 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 is an Execute tool because it triggers external operations—agent conversations that can invoke API calls and produce side effects—whose outcomes depend on user input. While not immediately destructive or financial, it has a high severity due to the potential for an AI agent to misuse natural language instructions to trigger unintended API operations.
From the tool's definition The tool description states 'Start a new conversation with an agent. Provide your message and the agent will respond.' This indicates it initiates and executes an agent interaction based on user-provided messages.
Documented attack patterns abuse exactly the kind of access start_agent_conversation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Automagik Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for start_agent_conversation:
{
"version": "1",
"default": "deny",
"tools": {
"start_agent_conversation": {
"limits": [
{
"counter": "start_agent_conversation_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} start_agent_conversation 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.
Start a new conversation with an agent. Provide your message and the agent will respond. It is categorised as a Execute tool in the Automagik Tools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for start_agent_conversation: 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 Automagik Tools. Nothing to install.
start_agent_conversation 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_conversation 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_conversation. 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_conversation is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Automagik Tools, 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.
122 Automagik Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.