neofs_create_container · Neo N3 MCP Server MCP

WHAT IT DOES

What neofs_create_container does on Neo N3 MCP Server

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

WHY IT NEEDS A POLICY

Why neofs_create_container needs a policy

This tool creates a new storage container on the NeoFS distributed storage system, which is a persistent, irreversible allocation of storage resources that may incur costs. While creation itself is reversible (containers can be deleted), the tool represents a Write action—it modifies the state of the distributed storage system by instantiating a new container.

From the tool's definition Tool name 'neofs_create_container' and description 'Create a new storage container (requires WIF)' indicate creation of a new storage resource. The requirement for WIF (Wallet Import Format) confirms this requires wallet authentication to perform the action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

neofs_create_container Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "neofs_create_container": {
      "limits": [
        {
          "counter": "neofs_create_container_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Neo N3 MCP Server, so you can run agents against it safely.

FAQ

Questions about neofs_create_container

What does the neofs_create_container tool do? +

[NeoFS] Create a new storage container (requires WIF). It is categorised as a Write tool in the Neo N3 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on neofs_create_container? +

Register the Neo N3 MCP Server MCP server in PolicyLayer and add a rule for neofs_create_container: 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 Neo N3 MCP Server. Nothing to install.

What risk level is neofs_create_container? +

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

Can I rate-limit neofs_create_container? +

Yes. Add a rate_limit block to the neofs_create_container 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 neofs_create_container completely? +

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

neofs_create_container is provided by the Neo N3 MCP Server MCP server (r3e-network/neo-n3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.