create_automation
Create an event-driven automation rule. When the trigger event fires, the actions execute automatically. Example:
This record as markdown: /tools/app-businys-mcp-server/create-automation.md
What create_automation does on Businys
AI agents invoke create_automation to trigger actions in Businys. 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.
Why create_automation is rated High
This tool creates automation rules that fire actions automatically in response to events. The core behavior is executing arbitrary actions without further human intervention, making it Execute category. Severity is high because a misconfigured automation could trigger unintended operations (e.g., sending emails, modifying records, generating invoices) across the platform repeatedly and at scale.
From the tool's definition 'Create an event-driven automation rule. When the trigger event fires, the actions execute automatically.'
Attacks that exploit this kind of access
The rule that runs create_automation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_automation, this is the rule to start with:
create_automation 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Businys, apply this rule, and every create_automation call is checked against it from then on.
Questions about create_automation
Create an event-driven automation rule. When the trigger event fires, the actions execute automatically. Example:. It is categorised as a Execute tool in the Businys MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Businys MCP server in PolicyLayer and add a rule for create_automation: 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 Businys. Nothing to install.
create_automation 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 create_automation 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 create_automation. 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.
create_automation is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
Across the catalogue