Manage AWS Glue Data Catalog tables with both read and write operations. This tool provides comprehensive operations for managing Glue Data Catalog tables, including creating, updating, retrieving, listing, searching, and deleting tables. Tables define the schema and metadata for data stored in ...
Single-target operation
Part of the Amazon Data Processing MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use manage_aws_glue_tables to create or modify resources in Amazon Data Processing MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call manage_aws_glue_tables repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Amazon Data Processing MCP Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
manage_aws_glue_tables:
rules:
- action: allow
rate_limit:
max: 30
window: 60 See the full Amazon Data Processing MCP Server policy for all 36 tools.
Agents calling write-class tools like manage_aws_glue_tables have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Manage AWS Glue Data Catalog tables with both read and write operations. This tool provides comprehensive operations for managing Glue Data Catalog tables, including creating, updating, retrieving, listing, searching, and deleting tables. Tables define the schema and metadata for data stored in various formats and locations. ## Requirements - The server must be run with the `--allow-write` flag for create-table, update-table, and delete-table operations - Database must exist before creating tables within it - Appropriate AWS permissions for Glue Data Catalog operations ## Operations - **create-table**: Create a new table in the specified database - **delete-table**: Delete an existing table from the database - **get-table**: Retrieve detailed information about a specific table - **list-tables**: List all tables in the specified database - **update-table**: Update an existing table's properties - **search-tables**: Search for tables using text matching ## Usage Tips - Table names must be unique within a database - Use get-table or list-tables operations to check existing tables before creating - Table input should include storage descriptor, columns, and partitioning information Args: ctx: MCP context operation: Operation to perform database_name: Name of the database table_name: Name of the table catalog_id: ID of the catalog (optional, defaults to account ID) table_input: Table definition search_text: Search text for search operation max_results: Maximum results to return next_token: A continuation string token, if this is a continuation call Returns: Union of response types specific to the operation performed. It is categorised as a Write tool in the Amazon Data Processing MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for manage_aws_glue_tables. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Amazon Data Processing MCP Server MCP server.
manage_aws_glue_tables is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the manage_aws_glue_tables 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 manage_aws_glue_tables. 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.
manage_aws_glue_tables is provided by the Amazon Data Processing MCP Server MCP server (awslabs.aws-dataprocessing-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.