aws___call_aws no longer exists - PLEASE Enable as CLI Tool call is a valid approach wrt python boto3

### Describe the feature

1 — aws___call_aws no longer exists
_resolve_via_mcp calls it. The endpoint answers:

{"jsonrpc":"2.0","id":2,"error":{"code":-32600,"message":"The call_aws tool has been removed, use another one."}}

We need this tool call as it helps for enterprise level Agentic Approach where tool calls are restricted for specific cli commands and which cannot be acheived through aws__run_script tool

### Use Case

We need this tool call as it helps for enterprise level Agentic Approach where tool calls are restricted for specific cli commands and which cannot be acheived through aws__run_script tool as a platform limitation as well.

Please help in enabling the aws___call_aws and let the customers handle how they need based on their use cases either cli commands tool or boto3 script tool.

This helps as enterprise customers restrict themselves with certain practices and helps ease them to use cli command tools.

### Proposed Solution

Enable aws___call_aws tool call Please

### Other Information

_No response_

### Acknowledgements

- [x] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

Start by tracing _resolve_via_mcp and the endpoint behavior described in the issue, then inspect where the aws___call_aws tool was removed or disabled. Confirm the supported approach for restricted CLI commands alongside aws__run_script, and verify that the endpoint no longer returns the tool-removed error without weakening the stated enterprise restrictions.

Written by the indexing model from the issue text.