Skip to main content
Glama
Sign In
operant-mcp

operant-mcp

Official
by operantlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

recon_s3_bucket

Test AWS S3 buckets for public access vulnerabilities by checking listing permissions and file readability to identify security risks.

Instructions

Test an S3 bucket for public access (listing, reading). Returns bucket_url, listable, listing_snippet, and readable_files. Read-only requests to S3.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bucket_name": "<bucket_name>"
    },
    "name": "recon_s3_bucket"
  }
}

Input Schema

NameRequiredDescriptionDefault
bucket_nameYesS3 bucket name to test, e.g. 'assets.example.com'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It effectively discloses key behavioral traits: it's a read-only operation (explicitly stated), performs security testing, and returns specific data fields (bucket_url, listable, listing_snippet, readable_files). It doesn't mention rate limits, authentication requirements, or potential side effects, but covers the core behavior well.

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 perfectly concise with two sentences that each earn their place: the first states the purpose and return values, the second clarifies the read-only nature. No wasted words, well-structured, and front-loaded with the core functionality.

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

Completeness4/5

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

For a single-parameter tool with no annotations and no output schema, the description provides good completeness: it explains what the tool does, what it returns, and its read-only nature. The main gap is lack of explicit output format details, but given the tool's relative simplicity, this is a minor omission.

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?

Schema description coverage is 100%, so the schema already fully documents the single 'bucket_name' parameter. The description doesn't add any additional parameter semantics beyond what's in the schema, maintaining the baseline score of 3 for high schema coverage.

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

Purpose5/5

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

The description clearly states the specific action ('Test an S3 bucket for public access'), the resource ('S3 bucket'), and the scope ('listing, reading'). It distinguishes from siblings by focusing on S3 bucket security testing rather than other recon or attack tools like 'recon_directory_bruteforce' or 'sqli_blind_boolean'.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: to test S3 buckets for public access vulnerabilities. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools, though the context implies it's for S3-specific reconnaissance.

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

Deploy Server

Other Tools