Medium Risk

create_data_processing_role

Create a new IAM role for data processing services. This tool creates a new IAM role with the appropriate trust relationship for the specified data processing service (Glue, EMR, or Athena). It can also attach managed policies and add an inline policy to the role. ## Requirements - The server m...

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 create_data_processing_role 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 create_data_processing_role 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.

amazon-data-processing-mcp-server.yaml
tools:
  create_data_processing_role:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Amazon Data Processing MCP Server policy for all 36 tools.

Tool Name create_data_processing_role
Category Write
Risk Level Medium

View all 36 tools →

Agents calling write-class tools like create_data_processing_role have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the create_data_processing_role tool do? +

Create a new IAM role for data processing services. This tool creates a new IAM role with the appropriate trust relationship for the specified data processing service (Glue, EMR, or Athena). It can also attach managed policies and add an inline policy to the role. ## Requirements - The server must be run with the `--allow-write` flag - The role name must be unique within your AWS account - Valid AWS credentials with permissions to create IAM roles ## Service Types - **glue**: Creates a role that can be assumed by the Glue service - **emr**: Creates a role that can be assumed by the EMR service - **athena**: Creates a role that can be assumed by the Athena service ## Common Managed Policies. add these policies - Glue: 'arn:aws:iam::aws:policy/service-role/AWSGlueServiceRole' - EMR: 'arn:aws:iam::aws:policy/service-role/AmazonElasticMapReduceRole' - Athena: 'arn:aws:iam::aws:policy/service-role/AmazonAthenaFullAccess' ## Usage Tips - Always provide a descriptive name and description for the role - Attach only the necessary managed policies to follow least privilege - Use inline policies for custom permissions specific to your use case - Consider adding S3 access permissions for data sources and targets Args: ctx: The MCP context role_name: Name of the IAM role to create service_type: Type of data processing service description: Optional description for the IAM role managed_policy_arns: Optional list of managed policy ARNs to attach inline_policy: Optional inline policy to add to the role Returns: CallToolResult: Information about the created role. 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.

How do I enforce a policy on create_data_processing_role? +

Add a rule in your Intercept YAML policy under the tools section for create_data_processing_role. 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.

What risk level is create_data_processing_role? +

create_data_processing_role is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_data_processing_role? +

Yes. Add a rate_limit block to the create_data_processing_role 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.

How do I block create_data_processing_role completely? +

Set action: deny in the Intercept policy for create_data_processing_role. 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.

What MCP server provides create_data_processing_role? +

create_data_processing_role 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.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.