AWS API MCP: `aws autoscaling describe-scaling-activities` does not reject `--max-records` parameter

[sumny]

Describe the bug

Agent calling aws autoscaling describe-scaling-activities via call_aws results in call_aws not rejecting --max-records although this parameter is not valid

Expected Behavior

call_aws with aws autoscaling describe-scaling-activities including --max-records should be rejected since it is not a valid parameter.

Current Behavior

Call is executed (--max-records is ignored) which can result in context blowing up if there are many autoscaling activies to fetch (they will be returned untrimmed).

Reproduction Steps

Have some autoscaling activies to fetch in account. Task an agent to make a call involving aws autoscaling describe-scaling-activities and explicitly force it to pass the --max-records parameter (and not the correct max-items; happened for me with Claude Sonnet 4.5). Observe that call_aws is executed and --max-records is not rejected which results in untrimmed autoscaling activies being returned.

Possible Solution

Should be caught by call_aws validation.

Additional Information/Context

No response

OS

macOS Tahoe 26.3.1

Server

aws-api-mcp-server

Server Version

No response

Region experiencing the issue

us-east-1

Other information

No response

Service quota

• I have reviewed the service quotas for this construct

[arnewouters]

AWS CLI seems to accept:

aws autoscaling describe-scaling-activities --auto-scaling-group-name prod-bucket-844892156532-us-east-1 --region us-east-1 --max-records 20

but rejects:

aws autoscaling describe-scaling-activities --auto-scaling-group-name prod-bucket-844892156532-us-east-1 --region us-east-1 --max-recordsa 20

At least the behavior is in line with AWS CLI, will have to dive deeper to understand why max-records is allowed when it's not described in the documentation.

(only tested on CLI v2)