Skip to main content
Glama
pickstar-2002

MinIO Storage MCP

delete_bucket_policy

Remove access policies from MinIO storage buckets to manage permissions and control data security configurations.

Instructions

删除存储桶策略

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketNameYes存储桶名称

Implementation Reference

  • Core implementation of the delete_bucket_policy tool handler. Ensures MinIO connection and sets an empty policy on the specified bucket to delete the existing policy.
    async deleteBucketPolicy(bucketName: string): Promise<void> {
      this.ensureConnected();
      await this.client!.setBucketPolicy(bucketName, '');
    }
  • src/index.ts:302-311 (registration)
    Registration of the 'delete_bucket_policy' tool in the MCP server's tools list, including name, description, and input schema.
      name: 'delete_bucket_policy',
      description: '删除存储桶策略',
      inputSchema: {
        type: 'object',
        properties: {
          bucketName: { type: 'string', description: '存储桶名称' }
        },
        required: ['bucketName']
      }
    }
  • MCP server request handler for 'delete_bucket_policy' tool. Parses input arguments using Zod and delegates to MinIO client, returning success response.
    case 'delete_bucket_policy': {
      const { bucketName } = z.object({
        bucketName: z.string()
      }).parse(args);
      
      await this.minioClient.deleteBucketPolicy(bucketName);
      return {
        content: [
          {
            type: 'text',
            text: `成功删除存储桶 ${bucketName} 的策略`
          }
        ]
      };
    }
  • Input schema definition for the delete_bucket_policy tool, specifying the required 'bucketName' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        bucketName: { type: 'string', description: '存储桶名称' }
      },
      required: ['bucketName']
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is a deletion, implying a destructive mutation, but doesn't clarify critical aspects: whether this is irreversible, what permissions are required, if it affects bucket functionality, or what happens on success/failure (e.g., returns confirmation or error). For a destructive tool with zero annotation coverage, this is a significant gap in safety and operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single phrase ('删除存储桶策略'), which is extremely concise and front-loaded with the core action. There is no wasted verbiage or redundancy, making it efficient for quick comprehension. Every word earns its place by directly conveying the tool's purpose without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (destructive mutation), lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral risks, success criteria, or error handling, which are crucial for safe invocation. While the purpose is clear, the absence of guidance and transparency makes it inadequate for a tool that permanently removes access controls, leaving the agent under-informed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with 'bucketName' documented as '存储桶名称' (bucket name). The description adds no additional parameter semantics beyond this—it doesn't explain format constraints, examples, or how the bucket name relates to the policy deletion. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema already provides adequate parameter documentation without extra value from the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '删除存储桶策略' (Delete bucket policy) clearly states the action (delete) and target resource (bucket policy), making the purpose immediately understandable. It distinguishes from siblings like 'delete_bucket' (deletes the bucket itself) and 'set_bucket_policy' (sets policy). However, it doesn't specify what a 'bucket policy' entails (e.g., access controls), which keeps it from a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., bucket must exist, policy must be set first), when not to use it (e.g., if you need to modify rather than delete), or refer to sibling tools like 'get_bucket_policy' to check current policy or 'set_bucket_policy' as an alternative. This leaves the agent with minimal context for decision-making.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pickstar-2002/minio-storage-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server