Get the metadata table configuration for a regular general purpose S3 bucket. Retrieves the metadata table configuration for a regular general purpose bucket in s3. This configuration determines how metadata is stored and managed for the bucket. The response includes: - S3 Table Bucket ARN - S3 ...
Part of the AWS S3 Tables MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_bucket_metadata_config to retrieve information from AWS S3 Tables MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_bucket_metadata_config only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_bucket_metadata_config:
rules:
- action: allowSee the full AWS S3 Tables MCP Server policy for all 16 tools.
Agents calling read-class tools like get_bucket_metadata_config have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get the metadata table configuration for a regular general purpose S3 bucket. Retrieves the metadata table configuration for a regular general purpose bucket in s3. This configuration determines how metadata is stored and managed for the bucket. The response includes: - S3 Table Bucket ARN - S3 Table ARN - S3 Table Name - S3 Table Namespace Description: Amazon S3 Metadata accelerates data discovery by automatically capturing metadata for the objects in your general purpose buckets and storing it in read-only, fully managed Apache Iceberg tables that you can query. These read-only tables are called metadata tables. As objects are added to, updated, and removed from your general purpose buckets, S3 Metadata automatically refreshes the corresponding metadata tables to reflect the latest changes. By default, S3 Metadata provides three types of metadata: - System-defined metadata, such as an object's creation time and storage class - Custom metadata, such as tags and user-defined metadata that was included during object upload - Event metadata, such as when an object is updated or deleted, and the AWS account that made the request Metadata table schema: - bucket: String - key: String - sequence_number: String - record_type: String - record_timestamp: Timestamp (no time zone) - version_id: String - is_delete_marker: Boolean - size: Long - last_modified_date: Timestamp (no time zone) - e_tag: String - storage_class: String - is_multipart: Boolean - encryption_status: String - is_bucket_key_enabled: Boolean - kms_key_arn: String - checksum_algorithm: String - object_tags: Map<String, String> - user_metadata: Map<String, String> - requester: String - source_ip_address: String - request_id: String Permissions: You must have the s3:GetBucketMetadataConfiguration permission to use this operation.. It is categorised as a Read tool in the AWS S3 Tables MCP Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_bucket_metadata_config. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS S3 Tables MCP Server MCP server.
get_bucket_metadata_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_bucket_metadata_config rule in your Intercept 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.
Set action: deny in the Intercept policy for get_bucket_metadata_config. 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.
get_bucket_metadata_config is provided by the AWS S3 Tables MCP Server MCP server (awslabs.s3-tables-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.