create_instance
A write tool on the Automagik Tools MCP server.
This record as markdown: /tools/namastexlabs-automagik-tools/create-instance.md
What create_instance does on Automagik Tools
AI agents use create_instance to create or update resources in Automagik Tools, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Automagik Tools environment.
Why create_instance is rated Medium
The tool name 'create_instance' strongly suggests creating a new instance of some entity (likely API configurations, agents, or connections given the server's purpose of transforming APIs into MCP agents). This is a reversible data modification (Write category).
From the tool's definition Tool name 'create_instance' indicates creation of a new resource or object. The verb 'create' is characteristic of Write operations that modify state by adding new data. No description provided to reveal destructive or execute-class behavior.
Attacks that exploit this kind of access
The rule that runs create_instance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Automagik Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_instance, this is the rule to start with:
create_instance 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Automagik Tools, apply this rule, and every create_instance call is checked against it from then on.
Questions about create_instance
create_instance is a write tool on the Automagik Tools MCP server. It is categorised as a Write tool in the Automagik Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for create_instance: 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.
create_instance 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 create_instance 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_instance. 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_instance 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.
More on Automagik Tools, and thousands of servers like it.
This server
Across the catalogue