manage_instances

A other tool on the Automagik Tools MCP server.

SERVERAutomagik Tools SOURCEnamastexlabs/automagik-tools

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/namastexlabs-automagik-tools/manage-instances.md

WHAT IT DOES

What manage_instances does on Automagik Tools

AI agents call manage_instances as a supporting operation in Automagik Tools workflows.

RISK

Why manage_instances is rated Low

The description is empty and uninformative, making it impossible to determine what this tool does with confidence. The name 'manage_instances' could span multiple categories — it could read (list instances), write (create/update instances), execute (start/stop instances), or even destructive (terminate instances). Given the ambiguity, 'Other' is assigned with low confidence.

From the tool's definition Tool name is 'manage_instances' with an empty description.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs manage_instances 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 manage_instances, this is the rule to start with:

manage_instances Rate-limited

manage_instances gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage_instances": {
      "limits": [
        {
          "counter": "manage_instances_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Automagik Tools, apply this rule, and every manage_instances call is checked against it from then on.

FAQ

Questions about manage_instances

What does the manage_instances tool do? +

manage_instances is a other tool on the Automagik Tools MCP server. It is categorised as a Other tool in the Automagik Tools MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on manage_instances? +

Register the Automagik Tools MCP server in PolicyLayer and add a rule for manage_instances: 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.

What risk level is manage_instances? +

manage_instances is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit manage_instances? +

Yes. Add a rate_limit block to the manage_instances 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.

How do I block manage_instances completely? +

Set action: deny in the PolicyLayer policy for manage_instances. 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.

What MCP server provides manage_instances? +

manage_instances 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.

KEEP EXPLORING

More on Automagik Tools, and thousands of servers like it.

This server

All 122 Automagik Tools tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →