Manage AWS Glue Data Catalog partitions with both read and write operations. Partitions in AWS Glue represent a way to organize table data based on the values of one or more columns. They enable efficient querying and processing of large datasets by allowing queries to target specific subsets of...
Accepts freeform code/query input (expression); 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_partitions 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_partitions 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_partitions:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Amazon Data Processing MCP Server policy for all 36 tools.
Agents calling write-class tools like manage_aws_glue_partitions 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 partitions with both read and write operations. Partitions in AWS Glue represent a way to organize table data based on the values of one or more columns. They enable efficient querying and processing of large datasets by allowing queries to target specific subsets of data. ## Requirements - The server must be run with the `--allow-write` flag for create-partition, update-partition, and delete-partition operations - Database and table must exist before creating partitions - Partition values must match the partition schema defined in the table ## Operations - **create-partition**: Create a new partition in the specified table - **delete-partition**: Delete an existing partition from the table - **get-partition**: Retrieve detailed information about a specific partition - **list-partitions**: List all partitions in the specified table - **update-partition**: Update an existing partition's properties ## Usage Tips - Partition values must be provided in the same order as partition columns in the table - Use get-partition or list-partitions operations to check existing partitions before creating - Partition input should include storage descriptor and location information Args: ctx: MCP context operation: Operation to perform database_name: Name of the database table_name: Name of the table partition_values: Values that define the partition partition_input: Partition definition max_results: Maximum results to return next_token: A continuation token, if this is not the first call to retrieve these partitions expression: Filter expression for list-partitions operation catalog_id: ID of the catalog (optional, defaults to account ID) 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_partitions. 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_partitions 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_partitions 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_partitions. 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_partitions 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.