Discover and describe AWS Glue connection types. This tool provides operations for discovering available connection types in AWS Glue and getting detailed information about specific connection types, including their supported properties, authentication methods, and compute environments. ## Oper...
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_connection_types 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_connection_types 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_connection_types:
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_connection_types 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.
Discover and describe AWS Glue connection types. This tool provides operations for discovering available connection types in AWS Glue and getting detailed information about specific connection types, including their supported properties, authentication methods, and compute environments. ## Operations - **describe-connection-type**: Get full details of a specific connection type including properties, auth config, and compute environments - **list-connection-types**: List all available connection types with brief descriptions ## Example ```python # List all available connection types manage_aws_glue_connection_types(operation='list-connection-types') # Describe a specific connection type manage_aws_glue_connection_types( operation='describe-connection-type', connection_type='JDBC' ) ``` Args: ctx: MCP context operation: Operation to perform connection_type: Name of the connection type (for describe-connection-type) max_results: Maximum results to return next_token: Pagination token 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_connection_types. 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_connection_types 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_connection_types 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_connection_types. 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_connection_types 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.