Manage AWS Glue crawlers to discover and catalog data sources. This tool provides comprehensive operations for AWS Glue crawlers, which automatically discover and catalog data from various sources like S3, JDBC databases, DynamoDB, and more. Crawlers examine your data sources, determine schemas,...
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_crawlers 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_crawlers 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_crawlers:
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_crawlers 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 crawlers to discover and catalog data sources. This tool provides comprehensive operations for AWS Glue crawlers, which automatically discover and catalog data from various sources like S3, JDBC databases, DynamoDB, and more. Crawlers examine your data sources, determine schemas, and register metadata in the AWS Glue Data Catalog. ## Requirements - The server must be run with the `--allow-write` flag for create, delete, start, stop, and update operations - Appropriate AWS permissions for Glue crawler operations ## Operations - **create-crawler**: Create a new crawler with specified targets, role, and configuration - **delete-crawler**: Remove an existing crawler from AWS Glue - **get-crawler**: Retrieve detailed information about a specific crawler - **get-crawlers**: List all crawlers with pagination - **batch-get-crawlers**: Retrieve multiple specific crawlers in a single call - **list-crawlers**: List all crawlers with tag-based filtering - **start-crawler**: Initiate a crawler run immediately - **stop-crawler**: Halt a currently running crawler - **update-crawler**: Modify an existing crawler's configuration ## Example ```python # Create a new S3 crawler { 'operation': 'create-crawler', 'crawler_name': 'my-s3-data-crawler', 'crawler_definition': { 'Role': 'arn:aws:iam::123456789012:role/GlueServiceRole', 'Targets': {'S3Targets': [{'Path': 's3://my-bucket/data/'}]}, 'DatabaseName': 'my_catalog_db', 'Description': 'Crawler for S3 data files', 'Schedule': 'cron(0 0 * * ? *)', 'TablePrefix': 'raw_', }, } ``` Args: ctx: MCP context operation: Operation to perform crawler_name: Name of the crawler crawler_definition: Crawler definition for create-crawler and update-crawler operations crawler_names: List of crawler names for batch-get-crawlers operation max_results: Maximum number of results to return for get-crawlers and list-crawlers operations next_token: Pagination token for get-crawlers and list-crawlers operations tags: Tags to filter crawlers by for list-crawlers operation 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_crawlers. 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_crawlers 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_crawlers 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_crawlers. 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_crawlers 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.