Medium Risk

crow_update_instance

Update a registered instance

How to control crow_update_instance ↓

What crow_update_instance does on Crow

AI agents use crow_update_instance to create or update resources in Crow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.

Medium Risk

Why crow_update_instance needs a policy

The tool performs an update operation on a registered instance within the Crow project management system. Updates are reversible modifications (Write category) rather than destructive deletions.

From the tool's definition Tool name includes 'update' which modifies existing data; description states 'Update a registered instance' indicating reversible modification of instance configuration or state.

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

How to control crow_update_instance

PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_update_instance:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "crow_update_instance": {
      "limits": [
        {
          "counter": "crow_update_instance_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about crow_update_instance

What does the crow_update_instance tool do? +

Update a registered instance. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on crow_update_instance? +

Register the Crow MCP server in PolicyLayer and add a rule for crow_update_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 Crow. Nothing to install.

What risk level is crow_update_instance? +

crow_update_instance is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit crow_update_instance? +

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

How do I block crow_update_instance completely? +

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

What MCP server provides crow_update_instance? +

crow_update_instance is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Crow tool call.

Start from Crow, 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.

576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.