manage_instances

THE RISK

Low Risk

Why manage_instances needs a policy

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.

Documented attack patterns abuse exactly the kind of access manage_instances gives an agent:

POLICY

How to control manage_instances

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

policy.json

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

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

Create a free account and register Automagik Tools — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Automagik Tools tools

Destructive delete_agent_conversation Delete a conversation session with an agent. This cannot be undone. Destructive delete_credential Delete a stored credential. Destructive delete_message Delete message for everyone. Only works for messages from you (from_me=True), within ~48 h Destructive delete_schedule Delete a schedule. Destructive delete_source Delete a workflow source. Destructive delete_task Delete a task execution. Destructive delete_team_collaboration Delete a team collaboration session. This cannot be undone. Destructive delete_workflow Delete a synchronized workflow.

All 122 Automagik Tools tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about manage_instances

What does the manage_instances tool do? +

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

Enforce policy on every Automagik Tools tool call.

Start from Automagik Tools, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →